Skip to main content
Glama
Sign In

Arbituro

by com.arbituro
OverviewDiscussionsAdmin

What happened

what_happened
Read-onlyIdempotent

The record of what has happened in a project recently — decisions, runs, approvals and changes, as one timeline. Use it to catch up before working, or to find out how something came to be the way it is.

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": {
      "project": "<project>"
    },
    "name": "what_happened"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoNarrow to one job by its key, e.g. FLAIR-12. Omit for the whole project.
projectYesThe project's key, e.g. FLAIR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that results are an aggregated recent timeline across event types, which is useful context beyond the annotations. It says nothing about how far back 'recently' reaches, pagination, or result limits, leaving real gaps for a timeline tool.

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

Conciseness5/5

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

Two sentences with no filler, and the core identity of the tool is front-loaded before the usage hint. Every clause carries information.

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?

For a two-parameter read-only tool with fully described schema and complete safety annotations, the description covers identity and purpose adequately. The only meaningful omission is the recency window and result volume, which an agent would need to interpret a timeline correctly.

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%, with both the project key and the optional job narrowing documented in the schema itself, so the baseline is 3. The description adds no syntax, default behavior, or scoping detail about the job filter beyond what the schema already states.

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 names a concrete resource — an aggregated activity timeline of decisions, runs, approvals and changes for a project — which lets an agent distinguish it from per-job tools like job_history or get_job. It stops short of explicitly naming a sibling to contrast with, so it is clear but not maximally differentiating.

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

Usage Guidelines4/5

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

It gives two concrete situations to use it: catching up before working, and tracing how something came to be. That is clear contextual guidance, though it offers no exclusions or explicit pointer to an alternative when the agent wants a narrower view.

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

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