Skip to main content
Glama

get_me

Read-onlyIdempotent

«Vos»: el retrato de la persona que arma Secondbrain con SUS reuniones (lo que dijo ella, medido por su huella de voz) y su historia de trabajo.

Trae, si existe: el retrato (quién sos, fortalezas, a mejorar con cómo,
foco, cómo sos en cada espacio, Eneagrama como hipótesis y cómo usar la
energía), el perfil de la semana con el tono de sus reuniones, los números
semana a semana (reuniones, cuánto habló, preguntas, intervenciones,
minutos y tono de -2 a 2) y lo último que dejó cada recap.

Para «¿cómo me fue en las reuniones?», «¿en qué tengo que mejorar?»,
«¿cómo vengo?». Sin huella de voz no hay material: decí que se registra en
la app (how_to_in_app("mi_voz")). Es del plan Hobby en adelante.

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_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
semanasNoCuántas semanas de números (default 12)
workspace_idNoUn workspace (UUID o nombre). Sin él, todos los de la persona.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive local operation, so the bar is lower. The description still adds real behavioral context beyond them: results are conditional ("si existe"), the tool returns nothing usable without a voice fingerprint, and availability is plan-gated. It does not discuss result size or latency, but for a read-only profile fetch that is a minor gap.

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?

The description is front-loaded: the first clause defines the resource before any enumeration. The long parenthetical inventory of portrait contents is dense but each item maps to a distinct returned field, so it earns its space given there is no output schema. The nested parentheses make it heavier than ideal, but nothing is redundant filler.

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?

With no output schema, the description must carry the return-value burden, and it does — enumerating the portrait dimensions, the weekly tone profile, the numeric metrics including tone scale of -2 to 2, and recap contents. Prerequisites, plan eligibility, and failure handling are all covered. The only remaining ambiguity is how the semanas and workspace_id parameters shape the returned payload, which is left implicit.

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%, and both parameters (semanas with default 12 and 4–52 bounds, workspace_id as UUID or name) are fully documented in the schema. The description only alludes to them indirectly through "los números semana a semana" and "cómo sos en cada espacio", adding no syntax, defaults, or interaction detail. Baseline 3 applies since the schema carries the 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 opening sentence names the resource precisely: the portrait of the person who builds Secondbrain from their own meetings, measured by voice fingerprint, plus their work history. It then enumerates the payload (portrait, weekly profile, week-by-week numbers, latest recap), which makes the tool's identity unmistakable. It does not explicitly name a sibling tool it is not, so it stops short of a 5.

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

Usage Guidelines5/5

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

It gives three concrete trigger questions ("¿cómo me fui en las reuniones?", "¿en qué tengo que mejorar?", "¿cómo vengo?") that map directly to invocation. It also states the blocking prerequisite — no voice fingerprint means no material — and routes the agent to the alternative action, telling the user to register in the app via how_to_in_app("mi_voz"). Plan gating ("Hobby en adelante") is disclosed as well.

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.

Resources