Skip to main content
Glama

port

Read-onlyIdempotent

Returns the route, tier, required gates, applicable lessons, and next commands for a target before editing, so AI agents know what proof a change owes.

Instructions

START HERE before editing a file: its route, tier, the gates to run, the lessons that apply, and the next commands. Successful structured results include the command record and exit code.

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": {
      "target": "<target>"
    },
    "name": "port"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesa file, a directory, or . for the tree.
runtimeNoa runtime_entry id, for --frame agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the shape of a successful result — the command record and exit code — which matters since there is no output schema. It leaves unexplained whether gates are merely listed or actually executed, a small ambiguity for a hint-marked read-only tool.

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?

Two sentences, zero preamble, and the actionable instruction is placed first. The closing sentence about structured results is a little vague in wording but still carries real information, so there is little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with no output schema, the description covers the entry point and the general contents of the response, which is roughly adequate. It leaves open what changes when 'target' is a directory versus a file, what a 'tier' means, and what happens on an unknown target.

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% for both parameters, so the schema already documents that 'target' accepts a file, directory, or '.' and that 'runtime' is a runtime_entry id. The description adds nothing further about either parameter, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource retrieved (route, tier, gates, lessons, next commands) but never states a verb such as 'get' or 'fetch' — the leading clause is usage guidance rather than a purpose statement. The name 'port' is opaque on its own, and nothing here distinguishes it from the sibling 'route' tool, so an agent must infer the function from context.

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?

'START HERE before editing a file' is an explicit, front-loaded when-to-use trigger that fires ahead of any edit. It gives no when-not condition and names no alternative among the siblings (route, gate, steps), so the routing side is incomplete even though the primary cue is clear.

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