Skip to main content
Glama
Sign In

Tevyon

by ai.tevyon
OverviewDiscussionsAdmin

Get job

get_job
Read-only

Status and results of a job. With wait_seconds it waits until the job is done or the time is up; call it again while the status is queued or running.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesFrom generate or list_jobs.
wait_secondsNoSeconds to wait for the job to finish (0 to 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world, so the safety profile is covered. The description adds the important non-obvious trait that this is a long-polling call that blocks up to wait_seconds, which the annotations do not convey.

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?

Two short sentences, front-loaded with what the tool returns before the polling mechanics. No filler, though the wait/poll behavior could be phrased slightly more crisply.

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

Completeness3/5

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

With only two well-documented parameters and no output schema, the description covers the essentials. It omits the result shape and any suggested retry cadence, and does not mention the 50-second cap that the schema carries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: wait_seconds is a blocking wait that returns either on completion or timeout, not just a delay value. It still does not explain what happens when wait_seconds is 0 beyond the schema default.

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 specific verb and resource (get a job) and states what it returns: status and results. It is clear enough to tell apart from list_jobs, though it never names that sibling explicitly.

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?

It gives real polling guidance: 'call it again while the status is queued or running' and explains what wait_seconds is for. It does not say when to prefer list_jobs over get_job, nor what to do on failure or terminal states.

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

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