Skip to main content
Glama

CarlNotes

Read Specials

read_dashboard
Read-only

Read a CarlNotes Specials page: Topic Specials across a person's topics, Podcast Specials across a person's podcasts, or Team Specials across a team's topics. It returns the summary of views or plays, Carl's paragraph about the month, the last day the snapshot counts, and the page's url. A team's Specials show only the summary to someone not on the team. Leave out userId or teamId for the connected account's own Specials or its first team. Use it when the user asks Carl for their Specials, how are my topics doing, how is my podcast doing, or how is my team doing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dashboardKind": "<dashboardKind>"
    },
    "name": "read_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdNoThe team whose Team Specials to read.
userIdNoThe person whose Topic or Podcast Specials to read.
selectionNoWhat the charts count, which the MCP view asks for. Leave it out.
dashboardKindYesWhich Specials: topics or podcasts for a person, or team for a team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses the return payload (views/plays summary, Carl's monthly paragraph, snapshot cutoff date, page URL) and a non-obvious permission behavior: a team's Specials show only the summary to someone not on the team. That access-trimming caveat is exactly the kind of context annotations cannot carry.

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?

Four sentences, front-loaded with the resource definition before return values and then usage triggers; each sentence carries distinct information. It is slightly dense — the return-value list is packed into one long clause — but nothing is redundant.

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?

For a read-only, 4-parameter tool with no output schema, the description covers purpose, mode selection, default argument behavior, return contents, and a permission caveat. There is no output schema, yet the return shape is described well enough that an agent knows what comes back.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real decision-level meaning the schema does not: what happens when userId or teamId is omitted (defaults to the connected account or its first team). It does not explain `selection` beyond the schema's own 'Leave it out' note, which keeps it from a 5.

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?

The description opens with a specific verb and resource ('Read a CarlNotes Specials page') and immediately enumerates the three distinct modes — Topic Specials, Podcast Specials, Team Specials — with their respective scopes (person's topics, person's podcasts, team's topics). An agent can map the required dashboardKind enum to these modes without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit trigger utterances ('how are my topics doing', 'how is my podcast doing', 'how is my team doing') and states the default routing rule: omitting userId or teamId yields the connected account's own Specials or its first team. This tells the agent both when to call it and how to call it with minimal input.

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.