Skip to main content
Glama
Sign In

Aimgod

by io.github.sendziuk
OverviewDiscussionsAdmin

Spheres

list_spheres
Read-onlyIdempotent

The user's spheres (life areas) with colors and sections; hidden_from_day marks a sphere kept out of the daily list. Planning spheres (used by tasks) by default; pass section for Goals, Focus, Visualisations or all. Fits when a task, goal or point needs a sphere, or the user asks about their areas.

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

Input Schema

NameRequiredDescriptionDefault
sectionNoWhich section's spheres: planning (default), goals, focus, visualisations or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section
      Added value: +{
+  "description": "Which section's spheres: planning (default), goals, focus, visualisations or all",
+  "enum": [
+    "planning",
+    "goals",
+    "focus",
+    "visualisations",
+    "all"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive behavior, so the description's value lies in explaining the default scope (planning spheres) and the meaning of the hidden_from_day flag. It adds useful semantics about what the results represent without contradicting the safety profile.

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 dense sentences, front-loaded with the resource and result content, then default behavior, then fit. There is no filler and every clause carries information.

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 simple, single-parameter read tool with full schema coverage and strong annotations, the description covers default behavior, result fields (colors, sections, hidden_from_day) and usage context. Without an output schema it could say a bit more about the returned shape, but nothing critical is missing.

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?

With 100% schema description coverage, the schema already enumerates all section values and notes planning as default. The description restates the same enum values and default, adding only the minor context that planning spheres are 'used by tasks,' which is marginal extra meaning.

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?

Starts with a specific verb and resource ('The user's spheres (life areas) with colors and sections') and clarifies which subset is returned by default. It does not explicitly name sibling list tools like list_goals or list_focus, but the resource is distinct enough that confusion is unlikely.

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 a clear when-to-use signal: 'Fits when a task, goal or point needs a sphere, or the user asks about their areas.' It also states the default section and how to override it. It lacks explicit when-not-to-use guidance or named alternatives, keeping it below a 5.

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

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