Skip to main content
Glama

save_assessments

Idempotent

Save requested assessments without changing status or replacing notes. Preview requests are read-only. Reuse retry IDs only with identical payloads. Reread skipped jobs.

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": {
      "assessments": "<assessments>"
    },
    "name": "save_assessments"
  }
}

Input Schema

NameRequiredDescriptionDefault
assessmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, and the description usefully confirms the non-destructive contract ("without changing status or replacing notes") plus the retry-ID reuse condition behind idempotency. It also reveals a partial-outcome behavior (skipped jobs must be reread) and a read-only preview mode, but leaves that mode unexplained and never describes failure handling or per-item versus all-or-nothing semantics.

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?

Four compact sentences with no filler and the non-destructive guarantee placed first. The sentences are telegraphic fragments, however, which trades brevity for ambiguity in "Preview requests" and "skipped jobs".

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 an idempotent batch mutation with optimistic-concurrency fields and no output schema, the description covers only part of what an agent needs: it omits how revision conflicts are handled, what a skipped job looks like in the response, and whether partial saves are possible. Combined with 0% schema coverage, meaningful gaps remain.

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 the single field is an array of Assessment objects with five nested properties (job_id, retry_id, revision, recommendation, reasoning) plus an enum and length limits. The description mentions retry IDs only glancingly and says nothing about revision semantics, the recommendation values, or the batch size cap, so it fails to compensate for the undocumented schema.

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?

"Save requested assessments" gives a verb and a resource, but "requested" is unexplained and the description never says this is a batch write of up to 25 assessment records. Nothing distinguishes it from siblings such as list_jobs_for_assessment or record_prepared_application, so an agent must guess from the name alone.

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?

The text offers operational caveats ("Preview requests are read-only", "Reuse retry IDs only with identical payloads", "Reread skipped jobs") but never states when to choose this tool versus an alternative, nor what prerequisites must hold before saving. An agent gets constraints, not routing guidance.

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.

Resources