Skip to main content
Glama

Read owned-brain priorities

read_priorities

Retrieve the PRIORITIES.md ranking policy from your owned brain to let the planner apply your natural-language prioritization rules.

Instructions

Return the full PRIORITIES.md (ranking policy) from the owned brain. The planner reads this as the natural-language ranking policy. Read-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": "read_priorities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does usefully declare read-only behavior and that the whole file is returned (not a slice). It omits what happens when the brain is unowned or PRIORITIES.md is absent, so error behavior is unstated.

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?

Three short sentences, front-loaded with what is returned and followed by consumer context. Nothing is redundant or padded.

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?

For a zero-parameter file read with no output schema, the description says enough: what is returned, that it is the full document, its purpose, and that it is read-only. Only edge-case behavior for a missing file is left undocumented.

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 nothing for the description to disambiguate beyond what the empty schema already conveys; baseline 4 applies.

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?

States a specific verb and resource: returns the full PRIORITIES.md, explicitly disambiguated as the 'ranking policy' from the 'owned brain'. An agent can distinguish it from read_goals/read_mission by the content described, though no sibling is named directly.

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

Usage Guidelines3/5

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

The line 'The planner reads this as the natural-language ranking policy' implies the usage context, but gives no explicit when-to-use vs when-to-skip guidance and never references the closely related read_goals or read_mission siblings.

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