Skip to main content
Glama

get_designated_school

Search and retrieve designated school recommendations from the secure student portal, filtering by prefecture, school, faculty, or deadline.

Instructions

Fetch designated school (指定校) recommendations from the secure student portal (/mypage/designated_school/index)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for search results (optional)
freewordNoFree word search (optional)
html_onlyNoReturn raw #main HTML instead of parsed data (optional, default: false)
prefecturesNoPrefecture filter codes (optional, e.g. [13] for Tokyo)
school_nameNoSchool name filter (optional)
faculty_nameNoFaculty name filter (optional)
school_typesNoSchool type codes: 1=university, 2=junior college, 3=vocational (optional)
freeword_exactNoMatch free word exactly (optional)
school_name_exactNoMatch school name exactly (optional)
faculty_name_exactNoMatch faculty name exactly (optional)
selection_deadline_beforeNoSelection deadline on or before YYYY/MM/DD or YYYY-MM-DD (optional)
Behavior2/5

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

No annotations provided, and the description only mentions 'secure student portal' implying authentication, but fails to disclose other behavioral traits like side effects, rate limits, or error handling.

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?

One sentence, front-loaded with action and resource, no wasted words. Perfectly concise.

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 11 parameters and no output schema, the description is too brief. It lacks information on return format, pagination, or error conditions, making it incomplete for the tool's complexity.

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 the schema already explains all parameters. The description adds no additional meaning beyond the schema, meeting the baseline.

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 clearly states 'Fetch designated school (指定校) recommendations' with a specific verb and resource, and distinguishes itself from sibling tools as no other tool fetches designated school recommendations.

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?

No explicit guidance on when to use this tool versus alternatives. However, since there are no directly competing sibling tools, the lack is acceptable but not ideal.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minagishl/nlobby-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server