Skip to main content
Glama

Read measured SwishrJobs performance

get_performance

Return the measured success rate, latency, and expected cost per accepted result for each capability, from controlled synthetic benchmarks. A capability that has not been benchmarked reports measured=false with a null success rate; no rate is ever invented. These are not customer outcomes.

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": "get_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
kindYes
staleNo
overallNo
serviceNo
versionNo
measuredYes
providerNo
age_secondsNo
capabilitiesYes
generated_atNo
provider_noteNo
methodology_versionNo
customer_results_includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / provider
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / provider_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and it does substantial work: it discloses data provenance (controlled synthetic benchmarks, not customer outcomes) and the null contract for unbenchmarked capabilities ('measured=false with a null success rate; no rate is ever invented'). It omits operational traits such as rate limits, caching, or auth requirements, which keeps it short of a 5 for an unannotated tool.

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?

Three short sentences, each earning its place: the first states what is returned and from where, the second defines the missing-data contract, the third pre-empts the most likely misreading of the numbers. The return payload is front-loaded before the caveats.

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?

With zero parameters and an output schema present, the description does not need to enumerate return fields, yet it still adds the interpretive context the schema cannot convey: synthetic origin and the meaning of measured=false/null. Nothing an agent needs to call this correctly or to avoid misusing the numbers is missing.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly introduces no argument surface and instead spends its words on output semantics.

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?

The description states a specific verb ('Return') and precise resources (measured success rate, latency, expected cost per accepted result) scoped to 'each capability' and sourced from 'controlled synthetic benchmarks'. That scope plus the explicit 'not customer outcomes' framing separates it cleanly from the submit_* and list_capabilities siblings without needing to name them.

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 implied rather than stated: an agent can infer this is the read used to compare capabilities on measured performance, and the note about unbenchmarked capabilities tells it what to expect. However, there is no explicit when-to-use versus alternatives (e.g. pairing with select_capability or list_capabilities) and no when-not-to-use guidance.

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