Skip to main content
Glama
Sign In

Arbituro

by com.arbituro
OverviewDiscussionsAdmin

Post a note

post_note

Leave a comment on a job, as yourself. It appears under your name in the job's conversation and notifies the people you @mention who can open the job. Naming an agent here starts nothing. Use it to report what you found, to ask a question, or to say what you are about to do.

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>",
      "job": "<job>",
      "body": "<body>"
    },
    "name": "post_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe job's key, e.g. FLAIR-12.
bodyYesThe comment, as markdown.
projectYesThe project's key, e.g. FLAIR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Well beyond the annotations, it discloses that the comment is attributed to the caller, appears in the job's conversation, and notifies @mentioned users who have access to the job. It also clarifies a negative behavior, that mentioning an agent triggers nothing, which prevents a plausible wrong assumption. It does not cover edit/delete follow-up or failure modes, so not a 5.

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 sentences, each carrying real information, with the core action front-loaded in the first sentence. The 'naming an agent here starts nothing' aside is slightly tangential but earns its place by preventing a specific misuse.

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 simple three-parameter write tool with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the key missing context: attribution, notification side effects, and non-triggering of agents. Only minor gaps remain around what happens to the returned result or on invalid job keys.

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?

All three parameters are fully documented in the schema at 100% coverage, including key formats and that body is markdown, so the schema carries the load. The description adds no further details about parameter formats, constraints, or interaction between project and job keys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Leave a comment on a job') plus the authorship framing ('as yourself'), which clearly separates it from read-only siblings like list_comments or job_history. An agent can identify the operation without opening the schema.

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 concrete situations for use ('report what you found, ask a question, say what you are about to do') and adds a useful scope boundary that naming an agent here starts nothing. It stops short of naming which sibling to use for related actions such as listing or updating comments, so guidance is clear but not exhaustive.

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