Skip to main content
Glama
ponisha-mcp

ponisha-mcp

by Kia-Karami

ponisha_list_project_bids

Read-only

List bids submitted to a Ponisha project, with visible details depending on employer access, so you can review proposals and compare offers.

Instructions

List the bids on a project (visible details depend on whether you are the employer).

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": {
      "project_id": "<project_id>"
    },
    "name": "ponisha_list_project_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/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 and reach profile is covered. The description adds one genuinely useful behavioral fact — that returned details depend on whether the caller is the employer — but says nothing about pagination behavior even though a page parameter exists.

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?

A single front-loaded sentence with no wasted words, and the important role-dependency caveat is placed immediately after the core action. Nothing is padded or restated from the tool name.

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?

With no output schema, the description should explain the return shape and paging, but only notes that visibility varies by role. It is adequate to identify the tool, yet leaves the pagination contract and the identity of the target project under-specified for a two-parameter read 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 carries the burden of explaining both parameters. It implies a project identifier via "on a project" but never clarifies the accepted string/number union, and it is entirely silent on the page parameter and its default of 1.

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 the bids on a project") and adds a scope qualifier that the details returned vary by caller role. It separates the tool from siblings like ponisha_get_bid (single bid) and ponisha_my_bids (own bids) implicitly through the resource, though it never names those alternatives.

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?

Usage is only implied by the resource name: an agent can infer this is the read path for enumerating bids on one project, but there is no explicit when-to-use guidance, no mention of when to prefer ponisha_get_bid or ponisha_my_bids, and no stated prerequisites such as authentication.

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