Skip to main content
Glama

CarlNotes

Read your account

read_account
Read-only

The connected account's CarlNotes plan and usage: the plan, this month's spend against the monthly budget with the shares where features pause, the day's scans against the daily limit, and the topic image regenerations left this month. Changing the plan or billing happens on carlnotes.com, whose links the result includes. Use it when the user asks Carl or CarlNotes about my plan, my usage, or how much budget is left.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds value beyond that: it states that the result carries links to carlnotes.com for anything mutating, and it names the specific data points returned, including threshold shares where features pause.

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?

Two sentences, front-loaded with the resource and its contents, then the usage condition. No filler, no restating of the title, and the redirect to carlnotes.com is placed where it matters.

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?

With no output schema, the description carries the return-value burden — and it does so by enumerating plan, spend vs. budget, pause thresholds, daily scans, and remaining regenerations. A brief note on behavior when no account is connected would close the last gap, but an agent has enough to call it correctly.

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 takes no parameters, so the baseline is 4 and there is nothing the description needs to disambiguate. The enumerated return content is a bonus rather than a substitute for parameter documentation.

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 names a specific resource (the connected account) and enumerates exactly what is read: plan, monthly spend vs. budget with pause thresholds, daily scans vs. limit, and remaining topic image regenerations. That distinguishes it well from read_dashboard or read_profile by scope, though it never names a sibling explicitly to route against.

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 an explicit trigger: 'Use it when the user asks Carl or CarlNotes about my plan, my usage, or how much budget is left.' It also carves out what this tool does not do — changing plan or billing happens on carlnotes.com — which is real exclusion guidance, but no sibling alternative is named for adjacent questions.

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.