Skip to main content
Glama

Show Me My Selfie

show_me_my_selfie
Read-only

The person's Selfie itemized within the seven KSA groupings: each statement in plain words, what it came from (their words, a life event, a document passage), its KSA Dictionary connection, their affirmation and their words, supporting evidence, and third-party verification (none is recorded in this POC). Proposed statements are marked as proposed. Beside the groupings: the person's interests in their own words and the possibilities they explored (occupations, certifications, programs, destinations), each with its source, the statements that support it with their affirmation, what prompted it and what it led them to describe. These are part of the person's record, kept distinct from the statements about what they have learned, and none is a qualification.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package": "<package>"
    },
    "name": "show_me_my_selfie"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYesThe package the last Selfie answer returned (goldribbon_package_v1 with its selfie_interview part). Keep it for the person and send it back whole; no copy is kept.
include_set_asideNoAlso show statements the person rejected or removed

Output Schema

NameRequiredDescriptionDefault
countsNo
limitsNoWhat this answer could not do, each { code, statement }
statusNoWhat happened, or needs_attention with a problem
packageNoThe person's package with the interview; absent when the call could not use it
problemNoWhen status is needs_attention: code, statement, what_to_do
contractYes
unplacedNo
groupingsNo
interestsNonote, and items: each interest's id, the person's words and the possibility it names
statementYes
distinctionsNo
next_actionsNo
explored_possibilitiesNonote, and items: each explored possibility's id, kind, code, title, source, prompted_by, supported_by (every observation's), led_to, and observations: each answer kept with its source, scope (page), captured_at, supported_by and the content it returned; a later capture of the same source and page names the earlier one it refreshes
described_not_yet_statedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / package / description
      Previous value: -"The package the last GoldSeam Selfie answer returned (goldribbon_package_v1 with its selfie_interview part). Keep it for the person and send it back whole; GoldSeam keeps no copy."New value: +"The package the last Selfie answer returned (goldribbon_package_v1 with its selfie_interview part). Keep it for the person and send it back whole; no copy is kept."
    • changedOutput schema / properties / next_actions / items / properties / tool / description
      Previous value: -"A GoldSeam service"New value: +"A service here"
  2. Changed3 schema fields changed
    • removedOutput schema / properties / explored_connections
      Removed value: -{
      -  "type": "object"
      -}
    • addedOutput schema / properties / explored_possibilities
      Added value: +{
      +  "description": "note, and items: each explored possibility's id, kind, code, title, source, prompted_by, supported_by (every observation's), led_to, and observations: each answer kept with its source, scope (page), captured_at, supported_by and the content it returned; a later capture of the same source and page names the earlier one it refreshes",
      +  "type": "object"
      +}
    • addedOutput schema / properties / interests
      Added value: +{
      +  "description": "note, and items: each interest's id, the person's words and the possibility it names",
      +  "type": "object"
      +}
  3. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine behavioral context beyond that: proposed statements are labeled as proposed, third-party verification is absent in this POC, and interests/possibilities are explicitly kept distinct from learning statements and are 'not a qualification.' However, it says nothing about volume, pagination, or whether the package must come from a specific prior tool.

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

Conciseness2/5

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

The text is a single ~120-word run-on enumeration with no lead sentence stating the action and no paragraph breaks. Much of it is a field-by-field inventory of return values, which duplicates what the output schema already provides. It is dense without being front-loaded.

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

Completeness2/5

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

The tool has an output schema and a nested-object package parameter, so the description needn't restate the return shape — yet nearly all of it does. Meanwhile the gaps that matter for correct invocation (when to call this versus the KSA view, where the package must come from, what include_set_aside yields) go unaddressed.

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 100% and the schema already explains both the package and include_set_aside parameters, so baseline 3 applies. The description adds nothing about either parameter — notably it never mentions include_set_aside, even though it describes showing rejected/removed statements only implicitly via 'proposed'.

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 description names the resource (the person's Selfie itemized across seven KSA groupings plus interests/possibilities), so an agent can infer this is a read/display operation. But there is no explicit verb stating what the tool does, and nothing distinguishes it from siblings such as my_selfie_ksa_view, my_selfie_checkpoint, or make_my_selfie. The result reads as a content inventory rather than a purpose statement.

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 when-to-use guidance, no prerequisites, and no named alternative. Given the crowded sibling set (my_selfie_ksa_view, my_selfie_checkpoint, make_my_selfie, add_to_my_selfie), an agent has no basis for choosing this tool over the KSA view or the checkpoint.

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.