ponisha-mcp

ponisha_get_project

Read-only

Retrieve full project details by ID—including budget, employer, status, bid credits, promotion costs, and hiring state—to assess whether a project is open or effectively closed.

Instructions

Get full details of a project by id (description, budget, employer, status). Includes coin_needed (credits a bid costs), promoted_coin_needed, and hiring: whether the employer already chose a freelancer. If hiring.already_hired is true the project is effectively closed even though its status says open (باز).

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_get_project"
  }
}

Input Schema

Name	Required	Description	Default
`extended`	No	Use the /extended endpoint (more data, may need login)
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 6, 2026

TDQS

A3.5/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 safety is covered. The description adds real domain semantics — coin_needed is the credit cost of a bid, and hiring.already_hired trumps the visible status — which is valuable. It says nothing about auth requirements beyond the schema's hint, or what happens for a missing/invalid id.

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?

Front-loaded with the core action, then layered with the credit-cost and hiring caveats. Three sentences, each carrying information; the inclusion of the Persian status token (باز) is a compact disambiguation rather than filler.

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?

With no output schema, the description usefully sketches the return shape (description, budget, employer, status, coin_needed, promoted_coin_needed, hiring) and flags the misleading-status case. The only notable omission is what extended mode yields and error behavior for an unknown id.

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?

Schema coverage is 50%: extended is documented in the schema, while project_id is only implied by "by id". The description never mentions the extended flag or what changes when it is set, so it neither fully compensates for the gap nor adds much beyond the schema.

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 ("Get full details of a project by id") and enumerates the returned facets (description, budget, employer, status). It implicitly contrasts with ponisha_search_projects by emphasizing lookup by id, but never names the sibling explicitly.

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 id-based framing implies you use this after finding a project via search, and the note about hiring.already_hired being effectively closed is genuinely useful context for deciding what to do next. However, there is no explicit when-to-use/when-not statement and no routing to ponisha_search_projects or ponisha_list_project_bids.

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

Deploy Server