Skip to main content
Glama

Find the voice profile

profile_lookup
Read-onlyIdempotent

Find a brand voice profile in Whalory's lookup order, from project files to the closest starter. Returns normalized JSON, learnings notes, and starter suggestions.

Instructions

Find the brand voice profile in Whalory's order: project VOICE.md/voice.json/voice/VOICE.md, ~/.whalory/profiles/, the skill's profiles, the closest starter. Returns the normalized JSON profile, the learnings note and starter suggestions.

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

Input Schema

NameRequiredDescriptionDefault
nameNoBrand or profile name, e.g. whalory, saas, en/saas
industryNoIndustry slug for the closest starter, e.g. saas
languageNo
project_dirNoProject folder; default: the first allowed folder
include_learningsNo

Output Schema

NameRequiredDescriptionDefault
pathNo
foundYes
sourceYes
profileNo
startersNo
warningsNo
learningsNo
markdown_pathNo
is_brand_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine value beyond them by disclosing the deterministic fallback chain (project files → user profiles → skill profiles → closest starter) and what the response contains (normalized JSON profile, learnings note, starter suggestions), which tells the agent the lookup degrades gracefully rather than failing.

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?

Front-loaded with the action, then a compact enumerated path chain, then the return summary. Nearly every clause earns its place; the sole weak spot is the vague phrase "the skill's profiles," which is less concrete than the other path entries.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them helpfully. Combined with annotations covering the safety profile and the description covering the search order, an agent has everything needed to invoke this correctly.

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 coverage is 60%, so the schema carries most of the burden; the description does not explain `include_learnings`, `project_dir`, or `language` at all. It only indirectly clarifies that lookup is keyed by brand name and that `industry`/starter selection drives the fallback, which is baseline-level added meaning.

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 gives a specific verb and resource ("Find the brand voice profile") plus the exact resolution order of locations searched. It is clearly distinct from the sibling tools (lint, playbook, reference, check_final), though it never names them explicitly to reinforce the contrast.

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?

Usage is only implied: an agent infers it should call this when it needs the voice profile. The resolution order is useful context, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative when a project-level profile already exists.

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