Skip to main content
Glama

Find student opportunities

find_opportunities
Read-only

Searches the public preview of the EduAvenues Student Opportunities database: summer programs, research programs, competitions, internships, scholarships and awards for middle and high school students. Filter by topic, grade, field, type, cost and selectivity. The preview is limited, so a short or empty list does not mean nothing matches; the full database link is included.

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

Input Schema

NameRequiredDescriptionDefault
ageNoStudent age
gradeNoCurrent grade
limitNoHow many results (default 8)
queryNoTopic or keywords, e.g. "math research" or "free summer engineering"
domainNoField
selectivityNoHow selective
cost_categoryNoCost
opportunity_typeNoKind of opportunity
application_effortNoHow much work the application takes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world, non-idempotent), and the description adds genuinely non-obvious behavior: results come from a limited preview, so short or empty lists are not proof of absence, and the response includes a link to the full database. It stops short of describing pagination behavior or result ordering, which keeps it from a 5.

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?

Two sentences, both front-loaded and functional: the first establishes scope and content, the second carries the important preview caveat. No filler or redundant restatement of the title.

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 nine-parameter, all-optional search tool with no output schema, the description covers scope, filterable dimensions, and the critical limitation that the dataset is a preview. Return shape details (limit default, ordering) are left to the schema and annotations, which is reasonable but leaves a small gap around result pagination.

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% with enums on five parameters, so the schema already documents every input. The description restates the filter axes ('topic, grade, field, type, cost and selectivity') without adding syntax, defaults, or combination semantics, and it omits age, limit, and application_effort entirely. Baseline 3 applies.

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 names a specific verb and resource ('Searches the public preview of the EduAvenues Student Opportunities database') and enumerates the covered content types (summer programs, research programs, competitions, internships, scholarships, awards) plus the target audience. It is clearly distinguishable from every listed sibling, though it never explicitly contrasts itself with an alternative tool.

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?

It implicitly tells the agent this is the search entry point for student opportunities and lists the filter axes available, but gives no explicit when-to-use/when-not guidance and does not route to or from any sibling tool. Adequate context, no exclusions.

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