ponisha-mcp

ponisha_update_skills

Replace the freelancer's verified skill list by supplying every skill ID and category ID to keep; any skill left out is removed, so fetch current IDs first.

Instructions

Replace your whole skill list (verified). Each item is {skill_id, skill_category_id}; get ids from ponisha_list_skills and your current skills (id, category_id) from ponisha_get_profile. Include every skill you want to keep: anything left out is removed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill_category_list": "<skill_category_list>"
    },
    "name": "ponisha_update_skills"
  }
}

Input Schema

Name	Required	Description	Default
`skill_category_list`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Discloses the critical behavior the annotations do not: this is a full replacement, and "anything left out is removed," which is the single most important thing an agent must know before calling. It also flags the list as "verified" and points to the source of truth for existing values. There is mild tension with destructiveHint=false since omission drops entries, but the operation replaces a user-controlled list rather than irreversibly destroying an entity, so this is disclosed behavior rather than a contradiction.

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?

Three short sentences, front-loaded with the replace semantics before the id-sourcing instructions and the removal warning. No filler; every clause carries actionable information.

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 one-parameter mutation with no output schema, the description covers input shape, id provenance, and the destructive consequence of omission. It does not say what the response contains or how partial/invalid ids are handled, which keeps it from a 5.

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 0% and the single array parameter is undocumented in the schema, so the description carries the burden — and it does, spelling out the item shape {skill_id, skill_category_id} and where each id comes from. It stops short of explaining validation rules (e.g., whether ids must exist or match category), leaving a small gap.

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 specific verb and resource: "Replace your whole skill list," which an agent can immediately distinguish from profile-editing siblings like ponisha_update_profile. It does not explicitly name a sibling it is not, so it falls just short of a 5.

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?

Gives concrete prerequisites: fetch ids from ponisha_list_skills and current skills from ponisha_get_profile before calling. It does not state when-not to use it (e.g., use update_profile for other fields), but the setup path is clear enough to act on.

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

Deploy Server