Skip to main content
Glama

Mike Reams: architecture writing, diagrams and toolbox

Search the site

search_site
Read-onlyIdempotent

Search Mike Reams's posts, work items, diagrams and agent skills by keyword. Returns titles, one-line summaries and canonical URLs, best match first.

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": {
      "query": "<query>"
    },
    "name": "search_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoLimit to one kind of page
limitNoMaximum results (default 10)
queryYesKeywords, e.g. 'CSDM application service' or 'AI governance'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "post",
      -  "work",
      -  "diagram",
      -  "page"
      -]New value: +[
      +  "post",
      +  "work",
      +  "diagram",
      +  "skill",
      +  "page"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing result ordering ('best match first') and the shape of each result item, which matters since there is no output schema.

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 sentences, both earning their place: the first covers scope and input mode, the second covers return format and ordering. Search scope is front-loaded with no filler.

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?

For a three-parameter read-only search with full schema coverage and complete safety annotations, the definition covers purpose, input mode, result contents and ranking. With no output schema present, the description correctly picks up the burden of describing what comes back.

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 description coverage is 100%: query, type enum and limit with min/max and default are all documented in the schema. The description only echoes the keyword concept ('by keyword'), adding no syntax, ranking or scoping detail beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb (search) and resource set (posts, work items, diagrams, agent skills) and lists the exact return shape: titles, one-line summaries, canonical URLs. It is clear what the tool does, though it never explicitly contrasts itself with the list_* siblings, leaving differentiation to inference from the word 'search'.

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

Usage Guidelines3/5

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

'by keyword' implies usage when the agent has keyword terms rather than wanting an enumeration, but there is no explicit when-to-use / when-not-to-use statement and no named alternative such as list_diagrams or get_page. The guidance is implied rather than stated.

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.

Resources