Skip to main content
Glama

get_advisor_guide

Read-only

Learn how to consult your family about a purchase, loan, or goal: what to ask, what each answer covers, and how to handle the data before using the advisor.

Instructions

The advisor guide: how to consult the family about a purchase, a loan or a goal, what to ask, what every answer covers and how to treat the data. Read it first, once per conversation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a non-mutating read, so the bar is lower; the description adds useful context about what the guide covers ('what to ask, what every answer covers and how to treat the data') and the once-per-conversation read cadence. It does not state the response format (plain text vs. structured) or approximate length, which would fully close the gap for a zero-parameter reference tool.

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?

Two sentences, zero filler, and the key operand — that this is the guide on consulting the family — is front-loaded before the imperative usage rule. Every clause adds information the agent needs.

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 simple, parameterless, read-only reference tool with no output schema, the definition supplies purpose, content scope, and ordering guidance, which is close to complete. The only meaningful omission is any hint about the shape or size of what comes back, which matters when an agent must decide how to budget context.

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; the baseline for a no-parameter tool applies. Nothing in the description misleads about inputs, and the schema correctly shows an empty, closed object.

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 identifies the resource precisely — an 'advisor guide' covering how to consult the family about a purchase, a loan, or a goal — and the instruction 'Read it first' makes the verb (fetch/read reference text) unambiguous. It is clearly distinguishable from the sibling tools, which are all data-mutating or proposal-oriented actions. It stops short of a 5 because it never explicitly says it returns the guide content rather than performing an action.

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?

'Read it first, once per conversation' is an explicit, actionable usage rule that tells the agent both the ordering (before other calls) and the frequency (a single read). What is missing is an explicit when-not or an alternative for agents that already have the guidance in context, but the cadence instruction covers most of the intent.

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