Skip to main content
Glama
Sign In
HullForge MCP Connector

HullForge MCP Connector

by jigwright
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Tool Schema

hf_tool_schema
Read-onlyIdempotent

Fetches exact arguments, full descriptions, and risk classes for up to 10 HullForge tools before execution, then returns the correct caller (hf_read, hf_write, or hf_destroy) to use.

Instructions

Exact arguments, full description and risk class of one or more HullForge tools, before you call them. Up to 10 names per call. Then call each tool through the caller this returns: hf_read, hf_write or hf_destroy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "names": "<names>"
    },
    "name": "hf_tool_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the 10-name batch limit and the fact that results include a risk class and a routing hint to the correct caller. It does not say how unknown or invalid names are handled, which matters for a lookup tool.

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

Conciseness5/5

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

Two short sentences with zero filler. The payload is front-loaded and the follow-up routing instruction comes second, in the order an agent needs it.

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?

For a single-parameter, non-destructive lookup with no output schema, the definition covers what goes in (tool names, up to 10) and roughly what comes back (arguments, description, risk class). Slightly more on the returned structure would make it fully self-sufficient.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the meaning, and it does: 'names' is clarified as tool names ('one or more HullForge tools') and the 10-item cap is restated, reinforcing the maxItems constraint. The item type and format of a valid tool name are still unstated.

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?

Specific verb and resource: it returns the exact arguments, full description, and risk class for named HullForge tools. That is clearly distinct from hf_read/hf_write/hf_destroy, which the description explicitly positions as the follow-up actions. It stops short of naming hf_search_tools as the discovery path for unknown tool names.

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?

Gives a clear usage trigger ('before you call them') and a clear next step ('Then call each tool through the caller this returns: hf_read, hf_write or hf_destroy'). It lacks any exclusion, such as what to do when you don't already know the tool name and should browse or search instead.

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

Deploy Server

Other Tools