Superintelligence.jobs

What changed

diff_since

Read-onlyIdempotent

Roles added or changed since an ISO timestamp — poll this on a schedule (heartbeat) instead of re-fetching the whole feed.

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": {
      "since": "<since>"
    },
    "name": "diff_since"
  }
}

Input Schema

Name	Required	Description	Default
`since`	Yes	ISO 8601 timestamp, e.g. 2026-10-29T00:00:00Z

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds the incremental-delta/polling behavior, which is genuinely useful context beyond the annotations. However, it doesn't describe what a polling consumer must do with the timestamp (e.g., advance the cursor to the latest returned timestamp), which is the key operational detail.

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 sentence with zero waste: what it returns is front-loaded, followed immediately by the recommended usage pattern. Nothing could be removed without losing 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 one-parameter read tool with no output schema, the description covers purpose, scope and operational pattern adequately. The only missing piece is cursor-advance semantics for a polling consumer, a minor gap given annotation coverage.

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 coverage is 100% and the schema already documents 'since' as ISO 8601 with a concrete example. The description's mention of 'ISO timestamp' adds nothing beyond the schema, so 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 (returns additions/changes) and resource (roles) scoped by an ISO timestamp. It implicitly differentiates itself from siblings like search_jobs or get_job by being a delta feed, but never names those alternatives.

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

Usage Guidelines5/5

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

Explicitly prescribes the usage pattern ('poll this on a schedule (heartbeat)') and states the alternative it replaces ('instead of re-fetching the whole feed'). An agent knows exactly when to pick this tool.

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

All Superintelligence.jobs tools Inspect

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

Need Help?