Skip to main content
Glama
Sign In
Examplary MCP Server

Examplary MCP Server

by examplary-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

practiceSpaces_list

List all practice spaces accessible in your workspace. Filter by folder or permission role to narrow results.

Instructions

Get a list of all practice spaces you have access to in this workspace.

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

Input Schema

NameRequiredDescriptionDefault
folderNoOptional filter by folder ID, e.g. `folder_1234`.
roleNoOptional filter by permission role.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.3

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It states 'Get a list' indicating a read operation, but does not address edge cases, pagination, or side effects. Adequate for a simple list tool.

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?

Single sentence, no fluff. Front-loaded with purpose. Efficiently communicates essential information.

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?

Given no output schema, description could hint at return structure, but 'list' is sufficient. Parameters are optional, so using no filters returns all. Minor gap: not specifying whether results are sorted or limited.

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 covers both parameters (folder and role) with descriptions. The tool description adds no extra meaning beyond the schema, placing it at 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?

Description clearly states 'Get a list of all practice spaces you have access to in this workspace', specifying verb, resource, and scope. It distinguishes from sibling tools like practiceSpaces_get (single space) and practiceSpaces_create.

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?

Provides clear context for use (listing accessible practice spaces) but does not explicitly mention when to avoid it or alternatives. Implicitly, filtering is supported via optional parameters.

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