Skip to main content
Glama
Sign In
become-human

become-human

by 201Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_profile

Retrieves the saved human profile so AI agents can recall user preferences, corrections, and working habits before making decisions.

Instructions

Everything learned about how your human works.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. The verb 'get' implies a safe read, but the description says nothing about output size, freshness, completeness (is 'everything' literally all accumulated data?), or what happens when no profile exists — all relevant for a full-dump retrieval.

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?

A single front-loaded sentence with no filler. The phrasing 'your human' is informal but not wasteful; the only cost is that brevity here shades into under-specification rather than crispness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument read tool without annotations or an output schema, the description is minimally sufficient — it hints at the return content. It still leaves the agent unsure how this differs from the other memory-reading siblings, which is the main completeness gap.

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 and the schema is trivially complete, so there is no parameter meaning for the description to add. Baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence 'Everything learned about how your human works' identifies the resource as accumulated knowledge about the user, so an agent can roughly guess the payload. However, it never uses the word 'profile', never states the scope (preferences? facts? history?), and does not distinguish it from siblings such as get_map or get_rules, which read as other kinds of stored memory.

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

Usage Guidelines2/5

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

There is no explicit guidance about when to call this versus get_map, get_rules, or where_is_my_data. An agent must infer that this is the personal-facts lookup, which is guesswork rather than instruction.

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

Deploy Server

Other Tools