Skip to main content
Glama
Sign In

Arbituro

by com.arbituro
OverviewDiscussionsAdmin

File a job

create_job

File a new job in a project. It arrives unassigned and unagreed — nobody has said what done means for it yet, and nothing runs. Use it for work you found that nobody has written down.

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>",
      "title": "<title>"
    },
    "name": "create_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort, imperative title.
projectYesThe project's key, e.g. FLAIR.
descriptionNoWhat the job is, as markdown. Say what you found and why it matters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely new behavior: the job is created unassigned and unagreed, and 'nothing runs' — i.e. creation has no execution side effect. It omits any auth/permission requirements, duplicate-handling behavior, or what identifier comes back.

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?

Three short sentences, front-loaded with the action and its state, with no boilerplate. The phrase 'nobody has said what done means for it yet' is flavorful and slightly indirect, but it does carry the 'unagreed' semantics efficiently.

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 creation tool with annotations present and no output schema, the description covers purpose, trigger, and the post-creation state. The main residual gap is the return value (e.g. the new job's identifier), which an agent calling this tool would likely want.

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%, so title, project key, and markdown description are already fully documented in the schema. The description adds no per-parameter meaning beyond nudging the agent toward recording 'what you found and why it matters,' which is marginal. Baseline 3 applies.

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 ('File a new job in a project') and immediately qualifies the state it lands in ('unassigned and unagreed', 'nothing runs'), which separates it from propose_job_update or claim_done. It never names a sibling explicitly, so differentiation is implied rather than stated.

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?

Gives a clear positive trigger: 'Use it for work you found that nobody has written down.' That is real when-to-use context, not a restatement of the name. It stops short of explicit exclusions (e.g. 'do not use this to modify an existing job — use propose_job_update'), leaving the agent to infer the boundary.

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