Skip to main content
Glama

Resolve one task to one checked record

unfragile_resolve
Read-only

Returns one checked record for a task, with its verdict, its Ed25519-signed passport and a paste-ready install line, or says that nothing qualifies.

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": {
      "intent": "<intent>"
    },
    "name": "unfragile_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesThe task, e.g. 'send a slack message from an agent'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real value by disclosing the response contents (verdict plus signed passport plus install line) and, importantly, the empty-result behavior ('says that nothing qualifies'), which tells the agent a miss is a normal outcome rather than an error. It stops short of describing error or latency behavior, so it is not a full 5.

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?

One front-loaded sentence with zero filler; the multi-clause payload list earns its space because the tool has no output schema. Slight denseness in the trailing list keeps it from being maximally crisp, but nothing is redundant.

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 one-parameter, read-only lookup with no output schema, the description covers what comes back and what happens on a miss, which is the essential contract. What is missing is the disambiguation from unfragile_find and any hint about how ambiguous intents are resolved, leaving the selection decision under-informed.

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% and the single 'intent' parameter carries its own example in the schema, so the schema does the heavy lifting. The description adds no constraints on the shape of the task string (e.g., how specific it must be, whether natural language keywords matter), so baseline 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?

The description uses a concrete verb and resource ('Returns one checked record for a task') and enumerates the payload: verdict, Ed25519-signed passport, paste-ready install line. The emphasis on 'one' signals single-result semantics, but it never contrasts itself with the sibling unfragile_find, so the agent must guess at the boundary between the two.

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 implied usage — resolving a described task to a single best-matching record — but no explicit when-to-use, when-not-to-use, or named alternative. With unfragile_find and unfragile_passport in the sibling set, the most important routing question (single resolve vs. broad find vs. passport lookup) is left unanswered.

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.