Skip to main content
Glama
Sign In

TestGraph

by io.github.BBCBasic
OverviewDiscussionsAdmin

Register a reusable field

register_field
Idempotent

Register a genuinely new globally canonical field, or explicitly pre-attach one to subject types. Do not ask the user for routine confirmation to reuse an existing canonical field: a valid existing field is attached automatically on first use. Prefer raw_text for one-off narrative detail.

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": {
      "canonical_name": "<canonical_name>",
      "json_schema": "<json_schema>",
      "subject_types": "<subject_types>"
    },
    "name": "register_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasesNo
descriptionNo
json_schemaYes
subject_typesYes
canonical_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / version_check
      Removed value: -{
-  "description": "Required live deployment token. Call get_server_info immediately before this write and pass write_version_token unchanged. Stale or missing tokens are rejected before any write occurs.",
-  "maxLength": 64,
-  "minLength": 64,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "canonical_name",
-  "json_schema",
-  "subject_types",
-  "version_check"
-]New value: +[
+  "canonical_name",
+  "json_schema",
+  "subject_types"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / version_check
      Added value: +{
+  "description": "Required live deployment token. Call get_server_info immediately before this write and pass write_version_token unchanged. Stale or missing tokens are rejected before any write occurs.",
+  "maxLength": 64,
+  "minLength": 64,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "canonical_name",
-  "json_schema",
-  "subject_types"
-]New value: +[
+  "canonical_name",
+  "json_schema",
+  "subject_types",
+  "version_check"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness, so the bar is lower. The description adds valuable behavioral context by explaining that existing canonical fields are attached automatically on first use and that explicit pre-attachment to subject types is allowed. It does not cover error behavior or permissions, but the added context is meaningful.

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?

Three sentences, front-loaded with the core purpose, followed by a usage guardrail and a preference rule. Every sentence earns its place, and there is no filler or redundant wording.

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

Completeness2/5

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

Despite strong usage guidance, the description omits all parameter semantics for a 5-parameter tool with a nested json_schema object and no output schema. An agent cannot reliably construct a valid call, especially the json_schema parameter, without additional information.

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

Parameters2/5

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

With 0% schema coverage, the description must compensate but only gestures at subject_types and canonical_name through phrases like 'globally canonical field' and 'pre-attach to subject types.' The required json_schema remains completely unexplained, and aliases/description are never mentioned, so an agent must guess how to construct the payload.

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?

States a specific action ('Register') on a specific resource ('a genuinely new globally canonical field') and contrasts it with pre-attaching to subject types. This distinguishes it clearly from siblings like register_subject_type_alias and makes the tool's scope unambiguous.

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

Usage Guidelines5/5

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

Explicitly says not to ask routine confirmation for existing canonical fields because valid existing fields attach automatically on first use, and tells users to prefer raw_text for one-off narrative detail. This provides clear when-to-use and when-not-to-use guidance.

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

All TestGraph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources