Fetch the current settings snapshot for the Settings app, optionally for a specific user, to let agents read live configuration.
Fetch the current settings snapshot for the Settings app.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| watching | No | ||
| gmail_email | No | ||
| subscriptions | No | ||
| push_available | No | ||
| gmail_connected | No | ||
| watch_expiration | No |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It correctly indicates a read-only operation ('fetch'), but lacks details on authorization needs or rate limits. Acceptable for a simple get tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is clear and to the point, with no wasted words or unnecessary details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema (which might detail return values) and the simplicity of the tool, the description is minimally adequate. However, it could elaborate on what 'settings snapshot' encompasses or any side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'user_id' is not described in the schema (0% coverage) and the tool description provides no explanation of its purpose or usage. The description fails to compensate for the missing schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches a 'current settings snapshot' for the Settings app. The verb 'fetch' and resource 'snapshot' are specific, and it easily distinguishes from sibling tools like settings.subscribe or settings.rotate_secret.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. Usage is implied as a basic retrieval operation, but there are no clues about prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.