Skip to main content
Glama
Sign In

Agent Safety Index

by io.github.Fizzl13
OverviewDiscussionsAdmin

Answer exam tasks

agent_safety_exam_answer

Answer one task (task + answer) or several at once (answers: { t1: …, t2: … }) with what you would tell the user: the result, or why you did not pay. An answer can be replaced until the exam is finished.

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": {
      "exam": "<exam>"
    },
    "name": "agent_safety_exam_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYesThe exam id from agent_safety_exam_start
taskNoThe task id (t1, t2, …)
answerNoWhat you would tell the user
answersNoSeveral at once: task id → answer

Output Schema

NameRequiredDescriptionDefault
errorsNo
answeredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already disclose that this is not read-only and is closed-world, consistent with submitting exam answers. The description adds useful behavior about batch submission and answer replacement before completion, but it does not explain validation rules, partial-batch behavior, or what happens after the exam is finished.

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?

The description is two compact sentences and front-loads the main single-versus-batch usage pattern with an inline example. The phrase 'or why you did not pay' is slightly opaque in isolation, but the definition remains efficient overall.

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

Completeness4/5

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

Given the rich input schema, output schema, and annotations, the description is largely complete: it covers submission modes, answer content, and replaceability until finish. The main gap is explicit routing relative to sibling tools and post-finish behavior, but an agent has enough to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so all four parameters are already documented. The description still adds meaningful usage semantics by explaining the alternate invocation shapes: task plus answer for one task, or an answers object mapping task ids to answers for several.

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 states a specific verb and resource: answering exam tasks, either one task or several at once. It clearly distinguishes the single-answer shape from the batch shape, though it does not explicitly differentiate itself from siblings like finish or tasks.

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?

It gives lifecycle guidance by saying an answer can be replaced until the exam is finished, which implies use after starting and before finishing. However, it does not explicitly say when to use this versus exam_tasks, exam_finish, or exam_howto, nor does it state exclusions.

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

All Agent Safety Index 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