Skip to main content
Glama
Sign In

knos

by io.github.drexthealpha
OverviewDiscussionsAdmin

One NEAR swarm job

knos_near_swarm_job
Read-onlyIdempotent

Reads one job from the jobs contract on NEAR testnet (jobs.knos-swarm-1105.testnet): its bid, the locked test's hash, which agent took it, what each submitted, and who was paid. Read only.

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": {
      "id": "<id>"
    },
    "name": "knos_near_swarm_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe job id, such as job-1105164458

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the marginal bar is lower, yet the description still contributes real context: the exact network and contract the read targets and the shape of data returned. The closing "Read only" merely restates the annotation, and nothing is said about behavior for a nonexistent job id.

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?

One sentence that front-loads the verb and resource, then lists return contents; no redundant preamble or filler. The trailing "Read only" is the only near-wasteful clause, and it is short.

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 single-parameter read with no output schema, the description supplies what an agent needs to invoke it and previews the returned fields, which compensates for the absent output schema. The only gap is undefined behavior when the id does not match an existing job.

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% and the single id parameter already carries a format example (job-1105164458) plus a 64-char bound. The description adds no further semantics about the id beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb and resource ("Reads one job from the jobs contract") and pins down the network and contract id (jobs.knos-swarm-1105.testnet). It also enumerates the returned fields (bid, test hash, taker agent, submissions, payouts), which cleanly separates it from listing-style siblings like knos_tasks or write siblings like knos_task_submit.

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?

Usage is only implied by the singular "one job" phrasing and the required id parameter; there is no explicit "use this when..." statement or named alternative for retrieving multiple jobs. An agent can infer it is the single-record lookup, but nothing in the text confirms or excludes cases.

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

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