Skip to main content
Glama
Sign In
procare-mcp

procare-mcp

by sanjibani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_school

Fetch a single school's details including name, address, phone, and hours using its unique ID.

Instructions

Fetch a single school by id (name, address, phone, hours, etc.).

Use when: "what's the address of school 1234?" or "what are the hours for our downtown location?"

Example: school_id="abc-123" returns {"id": "abc-123", "name": "..."}.

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": {
      "school_id": "<school_id>"
    },
    "name": "get_school"
  }
}

Input Schema

NameRequiredDescriptionDefault
school_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes the fetch operation and gives an example return, but does not discuss error handling, permissions, or what happens if the school is not found. It is transparent about the basic behavior but lacks full disclosure.

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?

The description is two sentences plus an example, all front-loaded and concise. Every sentence adds value without redundancy.

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?

Given the output schema exists (indicated in context signals), the description does not need to detail return values. The example return is sufficient. The description covers the main use case adequately.

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

Parameters4/5

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

Schema coverage is 0%, so the description must add meaning. It clearly states the parameter 'school_id' is used to identify the school and provides an example with 'abc-123', which adds context beyond the schema's type and title.

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 starts with 'Fetch a single school by id' which is a specific verb and resource. It lists fields (name, address, phone, hours) and distinguishes from sibling tools like get_child or get_classroom by focusing on school data.

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?

The description provides example query intents ('what's the address of school 1234?') and includes a concrete example. It does not explicitly state when not to use, but the examples give clear usage context.

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