Skip to main content
Glama
MeruLocal

raivatedu-mcp-server

by MeruLocal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List RaivatEdu Features

raivatedu_list_features
Read-onlyIdempotent

List RaivatEdu's nine product feature areas with their dedicated page URLs for a chosen market, optionally including page summaries for deeper research.

Instructions

List the product feature areas RaivatEdu documents, each with its dedicated feature page URL.

The nine feature areas are fixed site sections (Fee management, Students & batches, Admissions, Enrolment & renewals, Attendance, Certificates, Communication, Reports, Platform & security). Use raivatedu_get_page_content on a returned URL for the full write-up of a feature.

Args:

  • market (optional): locale for the URLs (in, us, gb, ca, au, nz, ie, sg, ae, za); defaults to the configured market.

  • include_descriptions (boolean): fetch each feature page's summary (default false).

  • response_format ('markdown' | 'json'): output format (default markdown).

Returns JSON shape: { "market": string, "count": number, "features": [ { "slug", "label", "url", "description"? } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoMarket/locale segment. One of: in, us, gb, ca, au, nz, ie, sg, ae, za. Defaults to the server's configured market (initially 'in' for India).
response_formatNoOutput format: 'markdown' for a human-readable summary (default) or 'json' for the full structured object.markdown
include_descriptionsNoIf true, fetch each page live to include its meta description (slower, one request per item). If false (default), return only verified labels and URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's added value is the cost disclosure that include_descriptions triggers per-page live fetches, plus the full return shape. That is genuine behavioral context beyond the structured fields, though it doesn't address failure behavior when a page fetch fails.

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?

Front-loaded with the one-line purpose and the fixed-section list, then Args and Returns in scannable blocks. No sentence is filler; even the parenthetical enumeration of the nine areas earns its place by setting agent expectations for the count.

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?

There is no output schema, and the description compensates by documenting the exact JSON shape including the optional description field. Combined with param semantics, sibling routing, and the fixed nine-item scope, an agent has everything needed to call and interpret this correctly.

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 all three parameters are already fully documented with enums and defaults. The description largely restates the schema ("market (optional): locale for the URLs", "include_descriptions (boolean)") with only marginal added meaning about what the locale affects.

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?

States a specific verb and resource ("List the product feature areas RaivatEdu documents"), then enumerates all nine sections so the agent knows exactly what the result set contains. Calling them "fixed site sections" differentiates this from the generic page/solution/resource listing siblings without opening their schemas.

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?

Explicitly routes the agent onward: "Use raivatedu_get_page_content on a returned URL for the full write-up of a feature," which tells it this is an index tool, not a content-retrieval tool. It stops short of naming when-not-to-use or contrasting with raivatedu_list_pages / list_solutions / list_resources.

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

Deploy Server

Other Tools