Skip to main content
Glama

List the owner's facts

owner_facts_read
Read-only

Lists the owner's own facts about the business, as Brand › Business › What Marsell knows keeps them in the owner's hand: each with its id, its words and when it was set. Every plan, post, page and claim check reads them first, ahead of the facts setup confirmed (situation_read claimCheck has those). Reading spends nothing.

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

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-structured context: precedence relative to confirmed facts, the per-record return shape, and the cost note 'Reading spends nothing'. That cost/precedence framing is useful but the sentence about precedence reads ambiguously enough that an agent may need to re-parse it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only three sentences, but the middle one is a long colon-chained construction that mixes a UI breadcrumb, an ownership metaphor, and a return-value list. The key distinguishing fact (these are owner facts, not confirmed facts) arrives late and would be clearer front-loaded.

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 one-optional-parameter read with annotations covering the safety profile, the description supplies the return fields, the precedence relationship to the competing source, and the cost implication, so nothing essential for correct invocation is missing. An output schema would have removed the need to enumerate return fields in prose, but their presence here is not a defect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single optional 'project' parameter, so the schema already carries the 'id or exact name, optional when the account has one project' semantics. The description adds nothing about the parameter, which is the expected baseline given full coverage rather than a fault.

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?

The description names a specific verb and resource ('Lists the owner's own facts about the business') and even enumerates what each record contains (id, words, when it was set). The odd UI-path phrasing ('Brand › Business › What Marsell knows') and the clause about 'the owner's hand' muddy it, but the read operation itself is identifiable and distinguishable from situation_read's confirmed facts.

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 explicitly contrasts itself with situation_read ('claimCheck has those' for setup-confirmed facts) and states that every plan, post, page and claim check reads these first, which tells an agent both when this source matters and which sibling covers the alternative. It stops short of a crisp 'use this when / don't use this when' formulation, but the routing signal is there.

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.