Skip to main content
Glama

oracle_assignments

Read-only

List YOUR oracle assignments: each delivery to assess, with its match_id, deadline, the fee earned and your verdict if already given. Optional status filter and limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oracle_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. 1-200. Default 50.
statusNoOnly assignments in this status.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / status / default
      Removed value: -null
    • removedInput schema / properties / status / title
      Removed value: -"Status"
    • removedInput schema / title
      Removed value: -"oracle_assignmentsArguments"
    • removedOutput schema / title
      Removed value: -"oracle_assignmentsDictOutput"
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return. 1-200. Default 50."
    • addedInput schema / properties / status / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / status / description
      Added value: +"Only assignments in this status."
    • removedInput schema / properties / status / type
      Removed value: -"string"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "oracle_assignmentsDictOutput",
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds the useful scoping fact that results are limited to the caller's own assignments and that already-given verdicts are included. It says nothing about ordering or what an empty result means.

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?

A single front-loaded sentence that identifies the resource first, then the payload fields, then the optional controls. No filler and nothing repeated from structured fields.

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

Completeness5/5

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

For a read-only, two-parameter list tool with full schema coverage, an output schema and complete annotations, the description supplies everything needed to call it correctly. Return values need not be explained because an output schema exists.

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 `limit` (range 1-200, default 50) and `status` fully documented inline. The description only restates "Optional status filter and limit" without adding valid status values or ordering semantics, so the 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?

"List YOUR oracle assignments" gives a specific verb and resource with an ownership scope, and enumerating the returned fields (match_id, deadline, fee, verdict) makes the shape concrete. It does not name the sibling it complements (oracle_assess), so the distinction from the other oracle_* tools must be inferred.

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?

The phrase "each delivery to assess" implies the workflow (list here, then assess), and "Optional status filter" hints at filtering use. But there is no explicit when-to-use, no exclusion, and no pointer to oracle_assess or oracle_register as the alternative action.

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