Skip to main content
Glama

feode-mcp

by com.feode

get_drill_string_guidance

Read-only

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)

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses behavioral traits such as returning reference image URLs for exact cell values instead of transcribing numbers. It aligns with the readOnlyHint annotation, indicating no destructive actions.

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

Conciseness3/5

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

The description is very long and dense, covering many details. It could be more structured (e.g., bullet points) but remains clear. Every sentence adds value, but brevity is lacking.

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

Completeness5/5

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

Given the absence of an output schema, the description thoroughly explains the return content (text guidance and reference images). It covers all listed topics and provides usage instructions, making it complete for a reference tool.

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 parameter 'topic' is fully described with a comprehensive list of allowed values and their meanings, adding significant value beyond the input schema.

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

Purpose5/5

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

The description explicitly states it provides NOV Grant Prideco drill-string guidance and reference data, listing many specific topics. It clearly distinguishes from sibling tools by its focus on drill string guidance and reference tables.

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 explains usage: call without a topic for everything or specify one topic. It does not explicitly mention when not to use or alternatives, but the context of sibling tools makes the usage clear.

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

All feode-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Tools are mostly distinct, but there is potential confusion between get_product_specs (product lines) and get_drill_pipe_specs (drill pipe items), as well as between list_drill_pipe and search_drill_pipe. However, descriptions clarify these differences.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, search_, submit_), making it predictable for agents.

Tool Count5/5

12 tools cover two main domains (FEODE company and drill string reference) without excess or deficiency, providing a well-scoped set.

Completeness4/5

The tool surface covers key operations for both domains: company info, product/service lifecycle, and drill string reference. Minor gaps like lack of company news or additional equipment categories, but core workflows are supported.

Resources