Skip to main content
Glama
ponisha-mcp

ponisha-mcp

by Kia-Karami

ponisha_list_portfolio

Read-only

Retrieve a user's portfolio items by username to review their freelance work and verify project experience.

Instructions

List a user's portfolio items.

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": {
      "username": "<username>"
    },
    "name": "ponisha_list_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own: nothing about pagination, result ordering, whether private/unlisted items are included, or whether this hits a public vs authenticated view (relevant given openWorldHint=true).

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

Conciseness4/5

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

One short, front-loaded sentence with zero waste. Its brevity is appropriate structurally, though the terseness borders on under-specification for a tool with an ambiguous sibling.

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

Completeness3/5

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

This is a low-complexity read with one parameter, annotations covering safety, and no output schema, so little explanation is strictly required. Still, the overlap with ponisha_get_portfolio and the undefined username format are gaps an agent would hit immediately when choosing and calling the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden for the single required parameter, and it only implies that "username" refers to a user. It does not state whether this is a Ponisha handle, a numeric id, or an email, nor whether the portfolio owner must be the caller.

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 gives a specific verb and resource: "List a user's portfolio items." An agent can tell it is a read of a portfolio collection rather than a project or skill lookup, but it never distinguishes itself from the sibling ponisha_get_portfolio, leaving ambiguity about whether this returns a collection or a single item.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — no statement of when to prefer this over ponisha_get_portfolio or ponisha_search_portfolio_tags, and no mention of prerequisites such as whether the portfolio must be public or whether auth is needed. The agent must infer the routing from the name alone.

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