Skip to main content
Glama
Sign In

concordance

by com.narrowhighway
OverviewDiscussionsAdmin

self_attest

[CHECK · internal] Record a person's OWN words about their study — a DISTINCTLY TYPED record that can NEVER count as a sealed check or satisfy an auto-graded requirement.

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": {
      "subject_id": "<subject_id>",
      "statement": "<statement>"
    },
    "name": "self_attest"
  }
}

Input Schema

NameRequiredDescriptionDefault
studyNo
statementYes
subject_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / statement / maxLength
      Added value: +4000
    • addedInput schema / properties / study / maxLength
      Added value: +4000
    • addedInput schema / properties / subject_id / maxLength
      Added value: +4000
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose one important behavioral trait: the record is distinctly typed and can never count as a sealed check or graded requirement. That is genuine value, but it omits permissions/auth needs, immutability or reversibility, and whether the write is idempotent for a mutation 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?

A single front-loaded sentence with no wasted clauses; the most important constraint (distinctly typed, non-counting) comes early. The all-caps emphasis is slightly noisy but does not pad the content.

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 3-parameter mutation tool with no annotations and no output schema, the description covers intent and one behavioral caveat but leaves subject_id semantics, authorization, and return expectations unexplained. Minimum viable, with clear gaps.

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% across three parameters, so the description must compensate. It only implicitly hints at 'statement' and 'study' (a person's own words about their study), and gives no meaning at all for the required 'subject_id', leaving a required parameter undocumented everywhere.

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: record a person's own words about their study. It also draws a sharp boundary against sibling concepts ('sealed check', 'auto-graded requirement'), which helps an agent separate it from attest_record/seal_fetch. It stops short of naming an alternative tool, so it is clear but not maximally discriminating.

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

Usage Guidelines3/5

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

The '[CHECK · internal]' tag hints at an internal-use scope, and the statement that the record can NEVER satisfy an auto-graded requirement implicitly tells the agent when not to reach for this tool. However, it never names the tool to use instead when a sealed/graded artifact is actually needed, leaving the routing to inference.

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

All concordance 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