Skip to main content
Glama

Read AI agent context

fleet__get_site_notes
Read-onlyIdempotent

The AI agent context the people in Royally wrote for you: the agency's house rules for every site (agency_notes), and each client's context (brand colors, tone, contacts, things not to touch). Read it before changing a site's content or design, and follow it unless the person you are working with says otherwise. With site_id: the agency context plus that site's client and its context (client is null when the site has none). Without site_id: the agency context plus every client that has context. For step-by-step instructions for a job, see skills__list. Reads Royally's records only.

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

Input Schema

NameRequiredDescriptionDefault
site_idNoA site id from fleet/list_sites, to get the notes that apply to that site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, and the description is consistent with all of them, reinforcing the closed scope with 'Reads Royally's records only'. It adds genuine behavioral detail beyond annotations by spelling out what is returned with versus without site_id, including that client is null when a site has no client.

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 purpose and the usage directive are front-loaded, and the with/without site_id behavior is stated in two tight parallel sentences. The parenthetical enumeration of client context fields adds useful concreteness at minor length cost, so it stops just short of maximum economy.

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 takes on the burden of describing return shape, and it does so for both call modes including the null-client edge case. For a single optional-parameter read tool with full annotation coverage, the only remaining gap is minor detail on formatting or volume of the notes payload.

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% and the schema already says site_id comes from fleet/list_sites, so the baseline is a 3. The description improves on that by explaining the semantic branching effect of the parameter: with site_id it returns agency context plus that one client's context, without it returns agency context plus every client that has context.

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 states a specific verb and resource: reading the AI agent context, split into agency-level house rules (agency_notes) and per-client context. It also distinguishes itself from skills__list by pointing there for step-by-step job instructions, so an agent can tell the two apart without opening either 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 an explicit trigger ('Read it before changing a site's content or design'), a precedence rule ('follow it unless the person you are working with says otherwise'), and names the alternative tool (skills__list) for procedural instructions. When-to-use, when-not, and the sibling alternative are all present.

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.

Resources