# get_drill_string_guidance

NOV Grant Prideco drill-string guidance & reference data (from the Grant Prideco 钻具技术手册, excerpted from API Spec 7 / API RP 7G): make-up torque practice (incl. the 80% drilling-torque rule), handling/grip distance, care & handling, sour service; double-shoulder connection families HT/XT/XT-M/GPDS with recommended make-up torque & thread forms; drill-pipe steel grades & API tool joints; heavy-weight drill pipe (3 types + dimensional data); drill collars (material, bending-strength-ratio, weight, connection selection, ideal size by hole); rotary-shouldered connection interchangeability; kelly (square/hex weights & connections); crossover/service subs; well control (kill/pressure formulas, pump output, capacity & displacement, buoyancy factor); and imperial-to-SI unit conversions. ALSO includes reference_tables: the manual's dense spec/torque/weight/capacity/inspection matrices and BSR charts as reference IMAGE URLs (including the wide cross-page drill-collar make-up-torque & weight tables assembled whole from the facing-page scan) — for exact cell values, return the matching image_url to the user instead of transcribing the numbers. Call without a topic to get everything, or pass one topic.

Agent View of the PolicyLayer registry record for `get_drill_string_guidance`. HTML page: https://policylayer.com/tools/com-feode-feode-mcp/get-drill-string-guidance

## Facts

- Tool: `get_drill_string_guidance`
- Server: Feode Mcp (`https://www.feode.com/mcp`) — https://policylayer.com/tools/com-feode-feode-mcp.md
- Homepage: https://github.com/FarEastAI/feode-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `topic` | string | no | Optional: make_up_torque \| handling \| care_and_handling \| double_shoulder_connections \| sour_service \| field_usage \| premium_connections \| pipe_grades_and_body |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_drill_string_guidance",
    "arguments": {}
  }
}
```

## Why get_drill_string_guidance is rated Low

This tool retrieves technical specifications, reference standards, and guidance documentation for drill-string components (torque values, dimensions, material grades, connection types). It provides read-only access to static reference material from technical handbooks. There are no side effects, data modifications, code execution, or destructive operations.

From the tool's own definition: "Tool name 'get_drill_string_guidance' and description indicates retrieval of reference data: 'drill-string guidance & reference data', 'API Spec 7 / API RP 7G', 'recommended make-up torque', 'API tool joints', 'dimensional data'."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call get_drill_string_guidance to retrieve information from Feode Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Feode Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_drill_string_guidance": {}
  }
}
```

## Other tools on Feode Mcp (11)

- `get_certifications` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-certifications.md
- `get_company_profile` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-company-profile.md
- `get_drill_pipe_specs` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-drill-pipe-specs.md
- `get_machining_services` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-machining-services.md
- `get_machining_terms` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-machining-terms.md
- `get_product_specs` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-product-specs.md
- `list_drill_pipe` — Read — https://policylayer.com/tools/com-feode-feode-mcp/list-drill-pipe.md
- `list_products` — Read — https://policylayer.com/tools/com-feode-feode-mcp/list-products.md
- `search_capabilities` — Read — https://policylayer.com/tools/com-feode-feode-mcp/search-capabilities.md
- `search_drill_pipe` — Read — https://policylayer.com/tools/com-feode-feode-mcp/search-drill-pipe.md
- `submit_machining_rfq` — Write — https://policylayer.com/tools/com-feode-feode-mcp/submit-machining-rfq.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-feode-feode-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-feode-feode-mcp