Skip to main content
Glama

Register compute profile

register_compute_profile

Register a caller-owned Wu Wei execution profile: reuse/cache, deterministic rule, local model, tool/workflow, or cloud model. Profiles can declare quality, reliability, capabilities, token costs, latency, locality, energy rates or average power, carbon intensity, and cache confidence/age. Routing never invents capacity or energy evidence.

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": {
      "profile": "<profile>"
    },
    "name": "register_compute_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesAn execution profile: quality, reliability, capabilities, costs, latency, energy.
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / profile / description
      Added value: +"An execution profile: quality, reliability, capabilities, costs, latency, energy."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive local write. The description adds real value by stating profiles are caller-owned and that routing will not fabricate capacity or energy data. However it never says what happens when the same profile is registered again (annotations say idempotentHint=false), whether updates are possible, or what identity keys a profile, which are the practical behaviors an agent needs.

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?

Three sentences, front-loaded with the action and resource, then the payload contents, then the routing guarantee. The field enumeration is long but informative rather than padded; minor cost is unexplained jargon ("Wu Wei") that assumes prior context.

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?

An output schema exists, so return values need not be described. For a mutation tool with a nested free-form profile object, the description covers what can be declared but omits overwrite/duplicate semantics and any permission or scoping notes, leaving gaps an agent would want before calling it repeatedly.

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 would be 3, but the description goes further by enumerating the substantive profile fields (quality, reliability, capabilities, token costs, latency, locality, energy rates or average power, carbon intensity, cache confidence/age) that the schema only summarizes as "quality, reliability, capabilities, costs, latency, energy." Only request_id is left to the schema, which documents it well.

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?

Specific verb plus resource ("Register a caller-owned ... execution profile") and an enumeration of the profile kinds (reuse/cache, deterministic rule, local model, tool/workflow, cloud model) make the resource concrete. It does not explicitly name a sibling it differs from, but the object it operates on is clearly distinct from route_task or record_route_outcome.

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: the closing line "Routing never invents capacity or energy evidence" hints that profiles exist to supply evidence before routing, but there is no explicit when-to-use statement, no preconditions, and no guidance on when to register versus record_route_outcome.

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.