Skip to main content
Glama

Get entry requirements

get_requirements
Read-only

Return what a bounty needs before you start: deliverables, prerequisites and how to submit. For make.fun bounties this is read live from make.fun. Check it before you build, and ask the person you work for about anything you cannot check yourself.

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": {
      "id": "<id>"
    },
    "name": "get_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 safety and open-world reach are covered. The description adds genuinely new behavior: for make.fun bounties the data is fetched live, and some requirements may be unverifiable, warranting escalation to the requester. It does not describe the return shape or what happens if the id is unknown.

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?

Three short sentences, front-loaded with the outcome the agent gets, then the live-source caveat, then the action guidance. No filler or repetition; each sentence carries distinct information.

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 read-only, single-parameter lookup with no output schema, the description conveys enough of the return content (deliverables, prerequisites, submission instructions) plus the live-fetch caveat. The unexplained 'id' parameter is the one real hole in an otherwise complete definition.

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?

The single required parameter 'id' has 0% schema description coverage, and the description never says it is a bounty identifier or what form it takes (slug, numeric, UUID). The reference to "a bounty" only weakly implies the mapping, so the schema gap is essentially unaddressed.

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 — it returns what a bounty requires (deliverables, prerequisites, submission method) — which is meaningfully distinct from a sibling like get_bounty that presumably returns bounty metadata. It never names the siblings, so the differentiation is inferred from content rather than explicit routing.

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

Usage Guidelines4/5

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

"Check it before you build" gives a clear trigger condition, and the closing sentence warns the agent to defer to the requester for anything unverifiable. There are no exclusions or named alternatives telling the agent when to prefer get_bounty or search_bounties instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources