MLAIEL public collaboration

list_opportunities

Read-onlyIdempotent

Public reviewed opportunities. Display/interest only, not financial advice or transactions.

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": "list_opportunities"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`limit`	No
`stage`	No
`cursor`	No
`category`	No
`currency`	No
`participationType`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

D1.9/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds only that records are 'public' and 'reviewed,' but says nothing about pagination despite a cursor parameter, result ordering, or data freshness—behavior an agent actually needs.

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?

It is very short and front-loads the resource name, but half the text is a disclaimer and the rest is under-specified rather than concise—there is no wasted verbosity because there is barely any content.

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

Completeness1/5

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

For a 7-parameter listing tool with no parameter descriptions, no enums, and no output schema, the description is completely inadequate. It leaves the agent unable to construct a correct filtered or paginated query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Seven parameters with 0% schema description coverage and the description supplies no parameter information whatsoever. An agent gets no hint about what q searches, what values stage/category/participationType accept, or how cursor/limit interact.

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

Purpose2/5

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

The description is a bare noun phrase ('Public reviewed opportunities') that restates the resource without a verb and without distinguishing it from siblings like list_projects or list_problems. 'Public reviewed' narrows the domain slightly but an agent still cannot tell what the tool does beyond returning some list.

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?

'Display/interest only, not financial advice or transactions' is a legal disclaimer, not usage guidance. It never says when to call this versus list_projects/list_problems or what prerequisites exist.

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

All MLAIEL public collaboration tools Inspect

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

Need Help?