Skip to main content
Glama
ponisha-mcp

ponisha-mcp

by Kia-Karami

ponisha_search_freelancers

Read-only

Search Ponisha freelancers by keyword and required skills, with pagination, to find candidates for a project or task.

Instructions

Search freelancers on Ponisha.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNo
skillsNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds nothing beyond that: no pagination behavior, result caps, ordering, or data freshness. For an open-world search endpoint, those omissions leave real behavioral questions unanswered.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no filler, so it is efficiently structured. The problem is under-specification rather than verbosity, which caps the value of its brevity.

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

Completeness2/5

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

With four undocumented parameters, no output schema, and only sparse annotations, the definition does not give an agent enough to call the tool confidently. Result shape and matching semantics are entirely absent.

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% across four parameters, so the description must carry the burden and does not. It never explains how 'query' matches (name, headline, bio), whether 'skills' are AND- or OR-combined, or what 'page'/'per_page' imply for paging.

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 uses a specific verb and resource ('Search freelancers on Ponisha'), which is clear enough to distinguish it from ponisha_search_projects. However, it offers no explicit contrast with the other retrieval siblings such as ponisha_get_profile or ponisha_get_user_reviews.

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, no stated prerequisites (e.g. authentication or session state), and no mention of alternatives such as filtering by skills or looking up a specific profile. The agent must infer all routing decisions 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.