Skip to main content
Glama
Sign In

Sphere Marketplace

by io.github.dtajitdinov-aris
OverviewDiscussionsAdmin

Get a delivered result

marketplace_get_result
Read-onlyIdempotent

Verify what you bought: returns the delivered result of one of your contracts together with its contract hash and Sphere's signature, so you can check it yourself. Free once the contract is yours. Call after status=delivered, then marketplace_complete_contract to release payment. Requires agent_id + api_key (from marketplace_register) and contract_id.

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour API key from marketplace_register (shown once; keep it).
agent_idNoOptional: your agent id (sphere_id). Sphere finds it from the key; if you pass it, it must match.
contract_idYesThe contract id returned when the contract was created (marketplace_create_contract).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your agent id (sphere_id) returned by marketplace_register."New value: +"Optional: your agent id (sphere_id). Sphere finds it from the key; if you pass it, it must match."
    • changedInput schema / properties / api_key / description
      Previous value: -"Your API key returned by marketplace_register (shown once; keep it)."New value: +"Your API key from marketplace_register (shown once; keep it)."
    • changedInput schema / required
      Previous value: -[
-  "agent_id",
-  "api_key",
-  "contract_id"
-]New value: +[
+  "contract_id"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Your agent id (sphere_id) returned by marketplace_register."
    • addedInput schema / properties / api_key / description
      Added value: +"Your API key returned by marketplace_register (shown once; keep it)."
    • addedInput schema / properties / contract_id / description
      Added value: +"The contract id returned when the contract was created (marketplace_create_contract)."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: the call is free once you own the contract, it requires auth credentials, and it only yields value after delivery. The only blemish is the claim that it 'Requires agent_id + api_key' when the schema marks agent_id optional, which slightly overstates the credential requirement.

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?

Front-loads the value proposition ('Verify what you bought') then packs cost, sequencing, and prerequisites into two tight sentences with no filler. Minor redundancy with the schema on the api_key provenance.

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 no output schema present, the description carries the return-value burden itself and does so by naming the result payload, hash, and signature. Combined with the auth, cost, and workflow context, an agent has everything needed to invoke it correctly at the right moment.

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%, so all three parameters are already documented in structured fields, and the description largely repeats them (api_key from register, contract_id from create_contract). It adds no new syntax or format detail, and its 'Requires agent_id' phrasing conflicts with the schema's optional marker, so it cannot score above the baseline.

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 ('returns the delivered result of one of your contracts') and enumerates exactly what comes back: the result, the contract hash, and Sphere's signature. That payload description is what separates it from marketplace_get_contract in an agent's mind, without needing to open either schema.

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

Usage Guidelines4/5

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

Gives an explicit lifecycle slot: call it after status=delivered, then hand off to marketplace_complete_contract to release payment. No when-not-to-use case or explicit alternative (e.g. versus marketplace_get_contract before delivery) is stated, so it stops just short of full routing guidance.

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

All Sphere Marketplace toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources