Skip to main content
Glama

brief_plan

Read-onlyIdempotent

Renders a sourced project brief from an already-validated geoprocessing plan; if validation fails, returns only the validation report instead of project text.

Instructions

Render a project brief from a plan that has ALREADY passed validation.

Every statement carries its source: operation declaration, argument rule, validation finding, engine availability or install requirement. Invalid plans return only the validation report and no project text. Installation commands are printed for the person to run; MapSmith never installs an engine.

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": {
      "plan": "<plan>"
    },
    "name": "brief_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • addedInput schema / $defs / OutputContract
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "What a branch promises to return, independently of its operation name.",
      +  "properties": {
      +    "cardinality": {
      +      "default": "unknown",
      +      "enum": [
      +        "one",
      +        "fewer",
      +        "more",
      +        "same_as_input",
      +        "unknown"
      +      ],
      +      "title": "Cardinality",
      +      "type": "string"
      +    },
      +    "geometry": {
      +      "anyOf": [
      +        {
      +          "enum": [
      +            "point",
      +            "line",
      +            "polygon"
      +          ],
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Geometry"
      +    },
      +    "kind": {
      +      "enum": [
      +        "vector",
      +        "raster",
      +        "table",
      +        "number",
      +        "map",
      +        "description"
      +      ],
      +      "title": "Kind",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "kind"
      +  ],
      +  "title": "OutputContract",
      +  "type": "object"
      +}
    • addedInput schema / $defs / PlanStep / properties / output
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/OutputContract"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Expected branch output: kind, optional geometry and cardinality"
      +}
  2. Addedv0.10.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety bar is low; the description still adds real value by stating that nothing is installed ('MapSmith never installs an engine') and that invalid plans yield only a validation report rather than partial text. These are output-behavior guarantees beyond what annotations convey.

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?

The key constraint (already-validated plan) is front-loaded in the first sentence, and the remaining sentences each carry a distinct behavioral fact. The 'Every statement carries its source' sentence is somewhat abstract but does communicate provenance in the rendered output.

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, return values need not be spelled out, and the description still covers the invalid-input path and the no-install guarantee. What is missing is any guidance on plan size/structure expectations or what the rendered brief looks like at a high level.

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?

The single 'plan' parameter is not described at the top level (0% schema description coverage per context signals), and the description says nothing about its shape or the '$step_id' reference convention. The nested $defs do carry their own field descriptions, so the gap is partially absorbed by the schema rather than fully compensated by the prose.

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 and resource ('Render a project brief from a plan') and adds a scope qualifier ('that has ALREADY passed validation') that separates it from validate_plan and execute_plan. It does not name those siblings explicitly, so an agent must infer the routing, but the operation itself is unambiguous.

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

Usage Guidelines4/5

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

The prerequisite ('ALREADY passed validation') plus the when-not case ('Invalid plans return only the validation report and no project text') gives clear usage context and a failure mode. It stops short of naming alternatives such as preview_map or execute_plan, so the agent still has to infer which output artifact it wants.

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