Skip to main content
Glama

Gantlett Systems - AI Governance Seam Pilots & Executive Briefs

Search Executive Architecture Briefings

search_executive_briefings
Read-onlyIdempotent

Search Gantlett Systems Inc. Executive Architecture Briefings covering brownfield AI velocity, zero-ASR agent containment, and sovereign local GPU economics. Use when retrieving CTO/VP Engineering executive briefings by topic. Do NOT use when checking fixed-fee 14-Day Seam Pilot commercial terms (use inspect_seam_pilot_scope 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": "search_executive_briefings"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional briefing keyword filter (returns all briefings when omitted).

Output Schema

NameRequiredDescriptionDefault
summaryYesDeterministic Markdown response summary.
matchCountYesNumber of matching executive briefings.
canonicalUrlYesCanonical documentation or twin URL for citation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / query / description
      Previous value: -"Optional topic keywords (lists all briefings when omitted)"New value: +"Optional briefing keyword filter (returns all briefings when omitted)."
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "brownfield",
      +  "local GPU",
      +  "security"
      +]
    • addedInput schema / properties / query / maxLength
      Added value: +120
    • addedInput schema / properties / query / minLength
      Added value: +2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "canonicalUrl": {
      +      "description": "Canonical documentation or twin URL for citation.",
      +      "type": "string"
      +    },
      +    "matchCount": {
      +      "description": "Number of matching executive briefings.",
      +      "type": "integer"
      +    },
      +    "summary": {
      +      "description": "Deterministic Markdown response summary.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "summary",
      +    "canonicalUrl",
      +    "matchCount"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety and idempotency profile is covered by structured data. The description adds topical scope but says nothing beyond the annotations about result ordering, limits, or the breadth of the corpus. With annotations carrying the behavioral load, this is adequate but not additive.

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

Conciseness4/5

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

Three short sentences, front-loaded with the resource identity, followed by the usage trigger and the exclusion. The topic-phrase list is dense marketing vocabulary but earns its place as keyword-match surface for an agent deciding relevance. No filler or repetition.

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-optional-parameter read-only search whose output schema exists and whose annotations cover safety, the description supplies the domain scope, the caller persona, and the routing exclusion. Nothing an agent needs to invoke it correctly is missing, though a note on result volume or ranking would round it out.

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?

There is a single optional 'query' parameter with schema description coverage at 100%, and the schema already states it is an optional keyword filter with min/max length and examples. The description adds no matching semantics (substring vs. full-text, case sensitivity) beyond the schema. Baseline 3 is correct where the schema does the heavy lifting.

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?

Names a specific verb (Search) and a specific resource (Gantlett Systems Inc. Executive Architecture Briefings) and enumerates the topic domains covered (brownfield AI velocity, zero-ASR agent containment, sovereign local GPU economics). An agent can distinguish this from the sibling tools without opening the 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?

Provides an explicit positive trigger ('Use when retrieving CTO/VP Engineering executive briefings by topic') and an explicit negative trigger with a named replacement ('Do NOT use when checking fixed-fee 14-Day Seam Pilot commercial terms -- use inspect_seam_pilot_scope instead'). This is exactly the when/when-not/alternative structure that routes selection.

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.