Skip to main content
Glama

Ask About Me — Personal Q&A

ask_about_me
Read-only

Get answers about a person's background, skills, projects, and interests by asking questions. Uses a comprehensive profile to provide information on career history, technical abilities, and personal details.

Instructions

Ask any question about this person and get an answer based on their complete profile. Covers: bio, career history, skills, projects, interests, personality, goals, and FAQ. Examples: 'What programming languages do they know?', 'Where do they work?', 'What books have they written?'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesAny question about this person (e.g. 'What are their top skills?', 'Do they have open-source projects?')

Implementation Reference

  • src/server.ts:82-117 (registration)
    Registration and handler implementation for the 'ask_about_me' MCP tool.
    server.registerTool(
      "ask_about_me",
      {
        title: "Ask About Me \u2014 Personal Q&A",
        description:
          "Ask any question about this person and get an answer based on their complete profile. " +
          "Covers: bio, career history, skills, projects, interests, personality, goals, and FAQ. " +
          "Examples: 'What programming languages do they know?', 'Where do they work?', 'What books have they written?'",
        inputSchema: z.object({
          question: z.string().describe("Any question about this person (e.g. 'What are their top skills?', 'Do they have open-source projects?')"),
        }),
        annotations: { readOnlyHint: true },
      },
      async ({ question }) => {
        const sections: string[] = [];
    
        for (const [category, data] of Object.entries(profile.data)) {
          if (data) {
            sections.push(`## ${category}\n${JSON.stringify(data, null, 2)}`);
          }
        }
    
        const context = sections.join("\n\n");
        return {
          content: [
            {
              type: "text" as const,
              text:
                `Question: ${question}\n\n` +
                `Below is the person's complete profile data. Use it to answer the question.\n\n` +
                context,
            },
          ],
        };
      },
    );
Behavior3/5

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

The description adds context beyond annotations by listing what the profile covers (bio, career history, skills, etc.) and providing example questions, which helps the agent understand the tool's scope. Annotations already declare readOnlyHint=true, so the agent knows it's a safe read operation. No additional behavioral traits like rate limits or auth needs are disclosed, but the description does not contradict annotations.

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

Conciseness5/5

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

The description is appropriately sized and front-loaded, with the first sentence stating the core purpose. Each subsequent sentence adds value by detailing coverage areas and providing examples, with zero wasted words. The structure is efficient and easy to parse.

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?

Given the tool's simplicity (1 parameter, 100% schema coverage, read-only annotation), the description is mostly complete. It covers purpose, scope, and examples. However, without an output schema, it does not explain return values or potential limitations, leaving a minor gap in contextual information for the agent.

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?

The input schema has 100% description coverage, so the schema already documents the 'question' parameter well. The description adds marginal value by reinforcing the parameter's purpose with examples (e.g., 'What programming languages do they know?'), but does not provide additional syntax or format details beyond what the schema states.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Ask any question about this person and get an answer based on their complete profile.' It specifies the verb ('ask'), resource ('this person'), and scope ('complete profile'), and distinguishes from the sibling tool 'search_profile' by focusing on Q&A rather than searching.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: for questions about the person's profile, with examples like 'What programming languages do they know?' However, it does not explicitly state when not to use it or mention alternatives, such as how it differs from 'search_profile' in terms of functionality or output.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paladini/mcp-me'

If you have feedback or need assistance with the MCP directory API, please join our Discord server