Skip to main content
Glama

More tools (free, no key)

sphere_more_tools
Read-onlyIdempotent

The rest of Sphere's tools (27): every paid service, selling your own service, the order steps after buying, chat, wallet and wanted orders. Free, no key. Returns each tool's name, description and inputSchema; call any of them directly by its name.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare this as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavior beyond that: no key is required, it returns name/description/inputSchema for 27 tools, and those tools are directly callable. It does not discuss ordering, pagination, or whether the set is stable, but for a zero-parameter discovery tool the coverage is solid.

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?

The description is short and front-loaded, starting with what the tool covers and then explaining the return shape and usage. The category list is useful rather than filler, though the phrase 'The rest of Sphere's tools' is slightly relative and could be tighter.

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 discovery tool with no input parameters and no output schema, the description explains what is returned and how to use the results. It covers the essential behavior an agent needs before calling it, with only minor omissions such as ordering or list completeness guarantees.

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 has zero parameters, so the baseline is 4. The description does not need to explain input semantics because there are none, and it appropriately focuses on output and follow-up invocation instead.

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 clearly identifies this as a catalog of Sphere's remaining tools and states what it returns: each tool's name, description, and inputSchema. It distinguishes itself from the sibling action tools by being a discovery/index tool, though 'the rest' is relative and the exact boundary is only clarified by the count and category list.

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?

It gives clear usage context: the tool is free, requires no key, and returned tools can be called directly by name. It does not explicitly say when to use this instead of directly invoking a known sibling, but the discovery use case is strongly implied by 'the rest of Sphere's tools' and the returned metadata.

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.