Skip to main content
Glama

adopt

Take a position as your current stance, date it today, and optionally attach a note to record the rationale.

Instructions

Adopt a position: I hold this. Dates it today.

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": {
      "position_id": "<position_id>"
    },
    "name": "adopt"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
position_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one useful trait, that the adoption is dated to today, but it says nothing about permissions, whether it mutates existing state, what happens on re-adoption of an already-held position, or whether the action is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the action, with no filler sentences. But it is compressed past the point of clarity, since "I hold this" conveys no operational meaning and the brevity reflects under-specification rather than tight writing.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. For a mutation tool with zero annotations and zero parameter documentation, however, the description should at minimum identify the target resource semantics and note the side effect of stamping today's date, which it only partly does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither of the two parameters is mentioned in the description. "position_id" is only weakly implied by the word position, and the optional "note" parameter is entirely undocumented in both schema and description, so the agent gets no guidance on what to pass in.

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?

"Adopt a position" names a verb and a resource, so the basic operation is inferable. However, the follow-on phrase "I hold this" is cryptic, and the description never draws the boundary against siblings such as reject or add, leaving the agent to guess which mutation records a stance.

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 prerequisites, and no mention of an alternative tool. The word "Adopt" hints at contrast with another sibling, but the description never states the condition that selects this tool over that one.

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