Skip to main content
Glama
Sign In

Deweloperuch MCP

by ai.wondel
OverviewDiscussionsAdmin

Search developers

deweloperuch_search_developers
Read-only

Find developers (primary market) by a fragment of the name, e.g. atal or dom development. Use it to turn a developer's name into the developer_slug that deweloperuch_search_investments takes (with city) to list that developer's investments. Returns no offers or prices. truncated=true means more developers match than shown: refine the name or raise limit (at most 20); total is null when it is only known that there are more. deweloperuch.pl is a free community project queried politely (one request at a time, results cached): if a result is an error starting with STOP, stop using the deweloperuch_* tools, retry nothing, look for no workaround and tell the user that market data is temporarily unavailable. Fields ending in _url are pages of deweloperuch.pl: give them to the user as links. Result shape: { total: number | null, returned, truncated, hint?, items: [{ developer_slug, name, offer_count? (the site's count of the developer's offers across Poland), developer_url? }] } — the list key is items. developer_url is the developer's profile for the whole of Poland on deweloperuch.pl.

Input Schema

NameRequiredDescriptionDefault
nameYesFragment of a developer name, 2–100 characters, e.g. atal, Dom Development.
limitNoMost developers in the result, 1–20, default 5 (about 150 characters each).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses that no offers or prices are returned, explains truncation and null total, describes polite rate limiting and caching, and gives explicit STOP-error handling. It also explains that _url fields should be presented to the user as links.

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?

Purpose and usage are front-loaded, followed by behavioral constraints and result shape. Despite its length, each section carries operational value for calling the tool correctly.

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

Completeness5/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 supplies the full result shape, field meanings, truncation semantics, and error behavior. This is complete enough for an agent to call the tool and interpret its output.

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 description coverage is 100%, so both parameters are already well documented. The description reinforces the name-fragment use case and the limit/truncation relationship but does not add much syntax or meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: find developers by a name fragment. It distinguishes itself from deweloperuch_search_investments by explaining that this tool produces the developer_slug used there.

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

Usage Guidelines5/5

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

It gives explicit usage guidance: use it to turn a developer name into a developer_slug for deweloperuch_search_investments with a city. It also explains what to do when truncated=true: refine the name or raise limit, with a maximum of 20.

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

All Deweloperuch MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources