Skip to main content
Glama
Sign In

goldseam

by com.ksaworks
OverviewDiscussionsAdmin

Compare Destinations

compare_destinations
Read-only

Line up 2 to 6 destination occupations side by side from one occupation: the bridge size (credential only, or the program bridges' awards as published), O*NET demand (median wage, outlook, bright outlook) and the evidence classes of the roads. Each cell is copied or counted, never scored.

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": {
      "from_soc": "<from_soc>",
      "to_socs": "<to_socs>"
    },
    "name": "compare_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_socsYes2 to 6 destination SOC codes, e.g. from find_transitions
from_socYesThe occupation compared from, e.g. 51-4121

Output Schema

NameRequiredDescriptionDefault
rowsNo
columnsNo
contractYes
statementYes
understoodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds a genuinely informative behavior: 'Each cell is copied or counted, never scored' and 'as published' nuance, clarifying that the tool presents data rather than evaluates it. This exceeds basic read-only disclosure.

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?

The description is two sentences, action-first, with no wasted words. Each phrase ('bridge size', 'O*NET demand', 'evidence classes') earns its place.

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 comparison tool with an output schema and readOnly annotation, the description sufficiently explains the comparison dimensions and the non-scoring behavior. The missing usage-vs-alternatives guidance is minor and does not prevent correct invocation.

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%, so the schema already documents both parameters with descriptions and examples. The description adds domain context by framing to_socs as 'destination occupations' and from_soc as 'one occupation', but it largely restates the schema semantics, so baseline 3 is appropriate.

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?

The description uses a specific verb 'line up' and names the resource 'destination occupations' plus the exact attributes compared (bridge size, O*NET demand, evidence classes). It distinguishes itself from compare_program_checklists by focusing on occupation destinations rather than checklists.

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 description implies the tool is for comparing 2–6 destination occupations from a single source occupation, but it does not name alternative tools or state when not to use it. It gives clear operational context (what is compared) but no explicit exclusions.

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

All goldseam toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources