Skip to main content
Glama

read_global_docs

Read shared AGENTS.md rules and cross-project memory at the start of any project work, so you follow standing user preferences and avoid asking for what they already state.

Instructions

The docs every project shares: the AGENTS.md for all projects (the user's standing rules) and the memory (facts and preferences that hold across projects), as markdown, then the caller's own rules and memory when they have any (they add to the team's; when they conflict, the team rule wins). Read them at the start of any work on a project and follow them; do not ask the user again for what they already say.

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_global_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does well: it states the return format (markdown), that the caller's own rules/memory are additive to the team's, and the precedence rule that team rules win on conflict. The main omission is edge-case behavior, e.g. what is returned when no global docs exist.

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 core content is front-loaded in the first clause, and each subsequent clause (precedence rule, usage directive) adds distinct information. It is a single dense, parenthetical-heavy sentence, which costs some readability but wastes no content.

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 zero-parameter read with an output schema present, the description supplies everything the agent needs: what is returned, the conflict-resolution rule, and the obligation to follow the content. Return-value structure is already covered by the output schema, so nothing material is missing.

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 zero parameters, so there is no parameter semantics to add and the baseline applies. The description correctly implies a parameterless, always-the-same fetch rather than hinting at filtering options that do not exist.

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 uses a specific verb (read) and enumerates exactly what the resource contains: the shared AGENTS.md standing rules and cross-project memory, plus the caller's own rules and memory. That enumeration distinguishes it from siblings like get_doc or list_docs, which retrieve individual documents rather than this composite of team-wide rules.

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 a clear directive on when to call it ('at the start of any work on a project') and an explicit follow-up behavior ('do not ask the user again for what they already say'). It stops short of naming when-not-to-call or a named alternative, but the trigger condition is unambiguous.

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