Skip to main content
Glama

Gantlett Systems - AI Governance Seam Pilots & Executive Briefs

Inspect 14-Day AI Governance & Seam Pilot Scope

inspect_seam_pilot_scope
Read-onlyIdempotent

Inspect the fixed-fee 14-Day AI Governance & Seam Charter Pilot deliverables, Step-0 nomos xray diagnostic, milestone schedule, and sector failure locks. Use when evaluating commercial pilot pricing, timeline, or deliverables. Do NOT use when searching technical whitepapers (use search_executive_briefings instead) or regulatory framework mappings (use inspect_compliance_and_sovereign_posture instead).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
sectorNoOptional industry sector filter for failure-mode locks.

Output Schema

NameRequiredDescriptionDefault
feeBandYesTransparent fixed-fee pricing band.
summaryYesDeterministic Markdown response summary.
durationYesFixed engagement duration.
canonicalUrlYesCanonical documentation or twin URL for citation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / sector / description
      Previous value: -"Optional sector filter: saas, aec, industrial, or regulated"New value: +"Optional industry sector filter for failure-mode locks."
    • addedInput schema / properties / sector / enum
      Added value: +[
      +  "saas",
      +  "aec",
      +  "industrial",
      +  "regulated"
      +]
    • addedInput schema / properties / sector / examples
      Added value: +[
      +  "saas",
      +  "regulated"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "canonicalUrl": {
      +      "description": "Canonical documentation or twin URL for citation.",
      +      "type": "string"
      +    },
      +    "duration": {
      +      "description": "Fixed engagement duration.",
      +      "type": "string"
      +    },
      +    "feeBand": {
      +      "description": "Transparent fixed-fee pricing band.",
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Deterministic Markdown response summary.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "summary",
      +    "canonicalUrl",
      +    "duration",
      +    "feeBand"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered structurally. The description adds only content-domain framing (fixed-fee pilot scope) and no extra behavioral detail such as data freshness or whether figures are static versus live. It adds modest value beyond the annotations, so a 3 is fair.

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, each earning its place: the first establishes scope, the second the positive trigger, the third the negative triggers with named alternatives. Nothing is padded or buried.

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?

With an output schema present and rich annotations, the description covers the remaining decision-relevant ground: what content is inspected and when to pick this tool. Minor jargon ('nomos xray', 'failure locks') is unexplained, but the surrounding text makes the intent recoverable.

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

Parameters3/5

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

Schema coverage is 100% and the single optional 'sector' parameter is fully documented with an enum and examples. The description only alludes to it via 'sector failure locks', adding no syntax or default semantics beyond the schema, so the baseline of 3 applies.

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 names a specific verb ('Inspect') and enumerates the concrete resource content: pilot deliverables, Step-0 diagnostic, milestone schedule, and sector failure locks. An agent can immediately distinguish this from search_executive_briefings and inspect_compliance_and_sovereign_posture without opening a schema.

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?

Explicit when-to-use is given ('evaluating commercial pilot pricing, timeline, or deliverables') and explicit when-not-to-use with two named alternatives, each paired with the condition that selects it. Routing is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.