Skip to main content
Glama

Marden Yard Permits

permit_detail

Scope, permit-declared value, status, dates, contractor and the raw source fields for one permit.

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": {
      "id": "<id>"
    },
    "name": "permit_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesjurisdiction/source permit id, e.g. chicago/B200517005

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description bears the full behavioral burden. It compensates partly by enumerating the returned content (scope, value, status, dates, contractor, raw source fields), which tells the agent to expect a wide record including unprocessed source data, but it says nothing about behavior for unknown ids, nulls, or result size.

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?

A single dense sentence with zero filler, and the 'one permit' scoping lands immediately. The fragmentary phrasing slightly weakens front-loading of the action, but nothing is wasteful.

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 one-parameter, non-mutating lookup with no output schema, listing the returned fields is essentially the needed completeness. Only error or missing-record behavior is left unaddressed, which is a minor gap.

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 id parameter already documents the jurisdiction/source format with a concrete example, so the schema does the heavy lifting. The description adds no further meaning about how the id is resolved across jurisdictions.

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?

Names the resource ('one permit') and its scope precisely, which separates it from the list-oriented search_permits and watch_area siblings. The only weakness is that it is a noun phrase listing returned fields rather than an explicit verb like 'get', but the intent is still unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no stated prerequisite such as needing a valid id from a search. The singular 'one permit' hints at detail lookup, but that must be inferred.

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