Skip to main content
Glama
FarEastAI

FEODE Capability Server

Official

get_drill_string_guidance

Read-only

Access drill-string guidance and reference data including make-up torque, handling, connections, drill pipe grades, drill collars, well control formulas, and unit conversions. Optionally specify a topic for focused information.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional: make_up_torque | handling | care_and_handling | double_shoulder_connections | sour_service | field_usage | premium_connections | pipe_grades_and_body | heavy_weight_drill_pipe | drill_collars | connection_interchange | kelly | crossover_subs | well_control | unit_conversion | reference_tables (dense spec/torque/weight/capacity/inspection matrices & BSR charts as reference image URLs)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation (which indicates safe read), the description adds key behavioral context: it returns reference data including image URLs and instructs to return the matching image_url instead of transcribing numbers. This goes beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely long, running as a single complex sentence with many semicolons and lists. While front-loaded with the main purpose, the structure is poor and contains excessive detail that could be better organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (many subtopics) and lack of output schema, the description covers most aspects: what data is included, how to use the topic parameter, and how images should be handled. It is fairly complete for an agent to understand usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only names the 'topic' parameter, but the description enumerates all 16 valid values (e.g., make_up_torque, handling, etc.) and briefly explains each. With 100% schema coverage, the description adds substantial meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides drill-string guidance from a specific source (NOV Grant Prideco manual) and lists many content areas. However, it is verbose and lacks a concise summary, but the verb 'get' plus resource 'drill_string_guidance' makes the purpose clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to call with or without a topic: 'Call without a topic to get everything, or pass one topic.' This provides clear invocation guidance, though it does not discuss alternatives or exclusions relative to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FarEastAI/feode-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server