MCP tools to query different aspects of Rahul Paul's job portfolio.
Scored across 6 tools
Each tool covers a distinct portfolio category—education, experience, overview, patents, projects, and skills—with no overlapping purpose. An agent can unambiguously select the right tool for each type of information.
All tool names follow a consistent single-word lowercase noun pattern, matching the portfolio domain. The naming is uniform and predictable.
Six tools is well-scoped for an AI engineer portfolio, covering the major sections one would expect without redundancy or bloat. Each tool earns its place.
The portfolio tool surface covers the core sections: background, experience, skills, projects, patents, and availability context. A contact/links tool could be a minor addition, but the set is functionally complete for exploring a candidate's profile.
Rahul's educational qualifications.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description carries the full burden of behavioral disclosure, yet 'Rahul's educational qualifications' only labels the content and says nothing about read-only behavior, side effects, permissions, or limitations. It is not misleading, but it provides no behavioral transparency beyond the tool's name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a tightly written four-word phrase with no filler, front-loading the core information. For a zero-parameter tool, this level of concision is appropriate.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is adequate for a simple no-parameter data view, and an output schema exists to define the return shape. However, it lacks any explicit relationship to sibling tools and does not clarify whether this covers degrees, certifications, or academic dates, leaving moderate ambiguity for an agent deciding between education and experience.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and 100% schema coverage (empty object), so there is no parameter semantic burden for the description to carry. The baseline of 4 applies because no parameter information is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource as 'Rahul's educational qualifications,' which is clear and distinguishes the tool from work-experience siblings like experience. It lacks an explicit verb (e.g., 'retrieves'), so it does not quite meet the top bar, but it is not a tautology and is unlikely to be confused with patents or projects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided: the description does not state when to choose education over experience, skills, or overview, nor does it mention any exclusions or alternatives. The only implied context is the word 'education,' which alone is insufficient guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Rahul's work experience / employment history, most recent first.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that results are ordered most-recent-first, which is a behavioral trait. However, it does not mention that the operation is read-only, nor any other side effects or constraints. For a simple retrieval tool, this is acceptable but not rich; the ordering note is useful but the description could also note the read-only nature.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the core purpose and adds the ordering detail. There is no waste; every word earns its place. It is appropriately short for a zero-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with no parameters and an output schema is present, so the description does not need to explain return format. It covers the content and ordering, which is everything an agent needs to decide whether to call it and what to expect. No missing information for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters and the schema is empty, so the baseline is 4. The description adds meaning beyond the empty schema by describing the content (work experience/employment history) and ordering (most recent first), which gives the agent context about what to expect from the output. Since there are no parameters to explain, the description suffices.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the resource ('Rahul's work experience / employment history') and implicitly the verb 'list' or 'retrieve'. It distinguishes itself from siblings like education, patents, and projects by topic. The ordering note adds specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context that this is for work experience, but does not explicitly state when to use it versus siblings or any exclusions. No alternative tools are named, so an agent must infer that this is the correct tool for employment history. The 'most recent first' note gives some usage context but not a full when-to-use guide.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
High-level overview: location, work mode, availability, preferred roles/domains, work authorization.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, what side effects (if any) occur, or how the overview is generated. The description only lists content areas, missing any safety or operational details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that efficiently communicates the tool's scope. It is appropriately sized for a parameterless tool with a straightforward purpose, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema (which explains return values) and the simplicity of the tool, the description covers the essential content areas. It does not miss anything critical for an agent to understand the tool's function, though it could be slightly more explicit about the read-only nature.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 covered at 100%. Per the baseline for 0 parameters, a score of 4 is appropriate; the description does not need to explain any parameter semantics since none exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: providing a high-level overview of location, work mode, availability, preferred roles/domains, and work authorization. It distinguishes itself from the sibling tools (education, experience, etc.) by being a summary rather than a specific category, though it does not explicitly name them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'High-level overview' implies the tool is used for a general summary rather than detailed specifics, but it does not explicitly state when to use it versus alternatives. No exclusions or conditions are provided, leaving the usage context implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Patents Rahul is named on.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral disclosure burden. It only states the content type and does not disclose whether this is a simple static list, any ordering, pagination, or limitations of the data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence with no wasted words, but it is so terse that it borders on under-specification rather than efficient conciseness. It is appropriately short but lacks substance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity (zero params) and an existing output schema, the description is nearly sufficient for a minimal list tool. It lacks explicit usage context, but the sibling-tool grouping makes the profile-section purpose clear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is trivially covered at 100%, so no parameter meaning is needed. The baseline of 4 for zero-parameter tools applies here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The noun phrase 'Patents Rahul is named on' clearly identifies the resource (patents) and the scope (those naming Rahul), distinguishing it from sibling profile sections like education and experience. It lacks an explicit verb like 'list' or 'show', but the intent is unambiguous in context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool instead of the sibling tools like projects or skills. The description only states what it shows, leaving an agent to infer usage from the name and profile context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Rahul's side/personal projects, with descriptions, tech stack, and links.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of disclosing behavior. It states what content is included but does not mention whether the operation is read-only, whether authentication is needed, or whether data is fetched live. For a simple project-listing tool these omissions are not severe, but the description adds limited behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the tool's purpose and lists the key contents. Every word contributes meaningful information, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with an output schema, the description covers the essential context: it identifies whose projects are included and what fields are returned. It could be slightly more explicit about the return shape, but the output schema likely fills that gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the input schema fully defines the invocation surface and there is nothing for the description to add. Per the baseline for zero-parameter tools, this dimension is adequately satisfied.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as Rahul's side/personal projects and specifies the content: descriptions, tech stack, and links. It lacks an explicit verb like 'list' or 'get', and does not explicitly differentiate from siblings, though 'projects' is distinct from education, experience, patents, skills, and overview.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: this tool is for accessing Rahul's side/personal project information. It does not explicitly name alternatives or state when not to use it, but the domain is specific enough for an agent to infer when this tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Rahul's skills, grouped by category (Languages, Frontend, Backend, AI & Agents, Cloud & Infra).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the grouping behavior and category names, which is useful. However, it doesn't state whether the output is a static list, whether it includes proficiency levels, or whether it's read-only. The lack of annotations makes this a moderate gap, but the description does add meaningful behavioral context beyond the empty schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that is front-loaded with the resource name and immediately provides the grouping structure. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only-looking tool with an output schema, the description is largely complete. It could mention that this is a static profile section or that it returns a categorized list, but the grouping and categories are already stated. The output schema likely covers the return structure, so nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is no parameter semantics burden. The description adds value by explaining the grouping and categories, which is the only meaningful semantic content. Baseline 4 for zero params is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear resource ('Rahul's skills') and a specific organizing principle ('grouped by category'), listing the categories. It distinguishes itself from siblings like education and experience by naming the resource and grouping. It doesn't use a verb like 'list' or 'show', but the intent is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for retrieving skills data, and the sibling names (education, experience, projects) suggest alternatives for other resume sections. However, it doesn't explicitly state when to use this tool versus a sibling, nor does it mention any context like 'use for skill-related queries'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
educationexperienceoverviewpatentsprojectsskills
Add one secure layer between your agents and this server.