franckelson-mcp

Who this is

get_profile

Read-only

Retrieve a person's profile details, including name, headline, location, time zone, languages, and professional summary, to quickly understand who they are and what they do.

Instructions

Name, headline, location, time zone, languages and a summary of what this person does.

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 26, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by listing the specific data fields returned, but it does not disclose any other behavioral traits (e.g., that the profile is for the current user or that it may be cached). No contradictions with annotations, but limited additional disclosure beyond the annotation.

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?

A single, efficient sentence that front-loads the key output fields. Every word contributes value, and the description is neither verbose nor under-specified. It is optimally concise for its purpose.

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

Completeness5/5

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

Given zero parameters, a readOnlyHint annotation, and no output schema, the description provides exactly what an agent needs: the list of fields returned. There is nothing missing for an agent to correctly invoke and interpret the tool's result.

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 has zero parameters, so the schema is trivially fully covered. Per the rubric, a 0-parameter tool gets a baseline of 4. The description adds no parameter-specific details because none exist, and it correctly focuses on the output content.

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 returns a person's profile: name, headline, location, time zone, languages, and a summary. This is a specific verb+resource (get profile) and distinguishes it from sibling tools like list_skills or get_contact by enumerating the exact fields returned. No ambiguity or tautology.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. It implies usage for fetching profile information, but there is no guidance on scenarios where a sibling like list_projects or get_availability would be more appropriate. Context is minimal but not misleading.

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

Deploy Server