Skip to main content
Glama
Sign In
mcpforwork

mcpforwork

by avivancos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

profile_gaps

Identifies missing profile sections and presents one actionable gap at a time to guide step-by-step completion without overwhelming forms.

Instructions

What the profile is still missing (required first, then progressive). Offer ONE gap at a time when contextually useful — never a form-wall.

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": "profile_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses ordering (required first, progressive) and an interaction style (one gap at a time, never form-wall), but doesn't explicitly state whether it's read-only or what the response looks like, though an output schema exists.

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?

Two compact sentences with a clear first sentence and actionable second sentence. No filler or redundancy.

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?

For a zero-parameter tool with an output schema, the description covers purpose, ordering, and interaction guidance. It could add an explicit read-only statement, but is otherwise sufficient for an agent to select and invoke it.

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 no parameters, so schema coverage is trivially complete. The description doesn't need to add parameter details; baseline for zero parameters is 4.

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?

The description clearly identifies the tool's function: exposing what's missing in a profile, with required items prioritized. It distinguishes itself from get_profile (current values) and update_profile (modification), though it lacks an explicit verb like 'list' or 'return'.

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?

Offers a usage pattern: present gaps one at a time when contextually useful, and never show a form-wall. However, it doesn't name alternatives or explicitly state when to use this over get_profile or resolve_field.

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

Deploy Server

Other Tools