Skip to main content
Glama

Read owned-brain mission

read_mission

Retrieve the full MISSION.md, the user's stable life-mission and intent, to align goal discussions and planning with their long-term mission. Read-only access from the owned brain.

Instructions

Return the full MISSION.md (the user's stable life-mission / statement of intent) from the owned brain. Read this when discussing or setting goals — goals ladder up to the mission. 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_mission"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does state that the operation is read-only and that it returns the full MISSION.md from the owned brain. It does not cover edge cases such as a missing mission file, permissions, or truncation, but for a zero-parameter read-only retrieval it discloses the key safety and source behavior.

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?

The description is front-loaded with the return value and source, then gives the usage context in a single compact clause. The trailing 'Read-only' is efficient and no sentence is wasted.

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 read-only tool with no output schema, the description covers what is returned, where it comes from, and when to use it. It could say more about behavior when no mission exists, but otherwise it is complete enough to invoke 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 has zero parameters, so the baseline is 4 and there is no parameter meaning to add. The description does not introduce any confusing parameter-like expectations.

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: return the full MISSION.md from the owned brain. It also explains what MISSION.md represents (stable life-mission / statement of intent), which disambiguates it from sibling goal and priority tools. The clause 'goals ladder up to the mission' further clarifies its role relative to goal-oriented siblings.

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 usage condition: read this when discussing or setting goals, because goals ladder up to the mission. It does not explicitly name alternatives such as read_goals or state when not to use this tool, so it falls short of full alternative routing.

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