Skip to main content
Glama
Sign In

MyLegend — public profiles, rich cards and personal agents

by io.github.falsalama
OverviewDiscussionsAdmin

Ask about a published person

ask_person
Read-only

Use this for a specific question about a resolved published person, including follow-ups to their displayed rich card. Answers use approved information. Ask explicitly for technical detail, equations or a derivation to receive longer approved material when available. A question-only request does not require a card. If a card is requested, use get_profile once. No raw CV or P3 data is exposed. If the user offers an agreed code word, pass only that supplied phrase unchanged as the current question; never guess or suggest phrases.

Input Schema

NameRequiredDescriptionDefault
slugYesPublished profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample.
historyNoUp to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts.
questionYesThe user's current question about this person's approved public information. Example: What do you do?
previousQuestionNoThe preceding question about the same person, only when needed to understand a follow-up. Example: What do you do?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / history
      Added value: +{
+  "description": "Up to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts.",
+  "examples": [
+    [
+      {
+        "content": "What is your research about?",
+        "role": "user"
+      },
+      {
+        "content": "An approved research overview.",
+        "role": "assistant"
+      }
+    ]
+  ],
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "content": {
+        "maxLength": 4000,
+        "minLength": 1,
+        "type": "string"
+      },
+      "role": {
+        "enum": [
+          "user",
+          "assistant"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "role",
+      "content"
+    ],
+    "type": "object"
+  },
+  "maxItems": 6,
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / slug / description
      Previous value: -"Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: danny-griffin."New value: +"Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample."
    • changedInput schema / properties / slug / examples
      Previous value: -[
-  "danny-griffin"
-]New value: +[
+  "morganexample"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare this a safe, non-open read (readOnlyHint=true, openWorldHint=false, destructiveHint=false). The description adds real behavioral context beyond them: answers use approved information only, no raw CV or P3 data is exposed, history does not authorise disclosure, and code words must be passed verbatim without guessing.

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?

Purpose is front-loaded and most sentences carry an actionable rule. A few clauses are dense and the code-word rule is bundled at the end, but there is little filler for the number of constraints being conveyed.

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 does cover the nature of returned content (approved material, longer derivations when explicitly requested, no raw CV/P3). It stops short of describing response structure or length limits, but is otherwise sufficient for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning by constraining how the question field is populated ('pass only that supplied phrase unchanged') and reinforcing that history is context-only, going slightly beyond the schema's own wording.

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?

States a clear verb+resource: answer a specific question about a resolved published person, including follow-ups to a rich card. It distinguishes itself from get_profile ('If a card is requested, use get_profile once'), but does not contrast with find_person, which is the natural upstream sibling.

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?

Explicitly says when a card is needed versus not ('A question-only request does not require a card'), routes card retrieval to get_profile, tells the agent to ask explicitly for technical detail to get longer material, and gives a concrete rule for handling an agreed code word.

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

All MyLegend — public profiles, rich cards and personal agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources