Skip to main content
Glama
ponisha-mcp

ponisha-mcp

by Kia-Karami

ponisha_list_skills

Read-only

Lists Ponisha skills with IDs, slugs, and titles, and lets you filter them by text; use returned slugs to narrow project searches.

Instructions

List all Ponisha skills (id, slug, title). Use slugs as filters in ponisha_search_projects.

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

Input Schema

NameRequiredDescriptionDefault
filterNoOnly return skills whose slug/title contains this text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/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 usefully discloses the returned field set, but says nothing about whether the list is complete or capped, how large it typically is, or whether results are cached — modest added value on top of the annotations.

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 short sentences, zero filler, with the core purpose front-loaded and the practical follow-up (slug reuse in search) second. Nothing is redundant or misplaced.

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 trivial zero-required-parameter read tool with no output schema, the description covers purpose, return shape, and downstream use — enough to call it correctly. Only the omission of result-size/pagination behavior keeps it from being fully complete.

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

Parameters3/5

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

There is a single optional parameter whose schema description ("Only return skills whose slug/title contains this text") is fully documented at 100% coverage. The description adds no matching semantics of its own, so the schema does all the work and the baseline 3 applies.

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 ("List all Ponisha skills") and even enumerates the returned fields (id, slug, title), which lets an agent distinguish it from sibling lookups like ponisha_list_categories. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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 second sentence ("Use slugs as filters in ponisha_search_projects") explains downstream usage, implying this is a reference/lookup tool to call before searching projects. It never states when not to call it, whether results are paginated, or whether ponisha_list_categories is the better choice for category-based filtering.

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