Paxaver

Get My Context

get_my_context

Read-only

Read-only lookup with no side effects - safe to call repeatedly. Requires authentication: returns only the caller's own context (never another user's data): first name, sign-in account email, account region, server environment, active school, the students they are a guardian for, and their role codes at that school. This is the context-discovery call - most other tools need a student_id or school_slug from here, admin-role checks come from roles, and email/region/environment answer which account is signed in. Returns live account state, so call again if the user may have switched schools or had roles changed.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`email`	No	Sign-in account email (the caller's own)
`roles`	No	Role codes the user holds at the active school
`region`	No	Region of the signed-in account
`students`	No	Students the user is guardian for (id, firstName, schoolSlug)
`firstName`	No	User first name
`schoolName`	No	Active school display name
`schoolSlug`	No	Active school slug
`environment`	No	Server environment - production, or dev for staging and development

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 17, 2026

addedOutput schema / properties / email

Added value: +{
+  "description": "Sign-in account email (the caller's own)",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / environment

Added value: +{
+  "description": "Server environment - production, or dev for staging and development",
+  "enum": [
+    "production",
+    "dev"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / region

Added value: +{
+  "description": "Region of the signed-in account",
+  "enum": [
+    "CA",
+    "US",
+    "MX",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedOct 3, 2026
RemovedOct 2, 2026
AddedSep 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only and non-destructive, and the description adds important behavioral context: authentication is required, only the caller's own context is returned, never another user's data, and live account state means it should be called again after school or role changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads safety and authentication before explaining usage, which is effective. The enumeration of returned fields is somewhat redundant because an output schema exists, but the overall structure is clear and each sentence still contributes useful context.

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?

For a zero-parameter, read-only discovery tool with annotations and an output schema, the description is complete. It covers authentication, data scoping, freshness, downstream dependency, and the meaning of key returned fields, leaving no meaningful gap for correct invocation.

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?

The tool takes no parameters, so the baseline is 4. The description does not need to explain parameter semantics, though it does describe the returned fields, which is output information rather than parameter guidance.

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 read-only lookup and enumerates exactly what caller context is returned, including name, email, region, environment, school, students, and role codes. It clearly distinguishes itself from siblings by naming its role as the context-discovery call that supplies student_id and school_slug for most other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says this is the context-discovery call and explains the downstream dependency: most other tools need student_id or school_slug from here, admin-role checks come from roles, and account identity comes from email/region/environment. It also gives a clear re-call condition when the user may have switched schools or had role changes.

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

All Paxaver 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?