get_scope
Read-only
Read this first. Describes when to use this MCP server vs web search. Call this at the start of any new conversation or when unsure which tool to use.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Jennifer Rebholz, Attorney - Knowledge Base
TDQS
A4.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations show readOnlyHint=true, consistent. Description adds context of being a first-step guide, beyond what annotations provide. No contradiction.
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?
Two sentences, front-loaded with 'Read this first.' Zero wasted words.
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?
Complete for a read-only guidance tool with no parameters or output schema. Covers when and why to use.
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?
No parameters; schema coverage 100%. Description need not add parameter info. Baseline 4 for 0 parameters.
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 explicitly states it describes when to use the MCP server vs web search. Clear verb and resource: guides tool selection.
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 'Call this at the start of any new conversation or when unsure which tool to use.' Differentiates from web search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool targets a distinct aspect of Jennifer Rebholz's professional profile (e.g., bio, biography, career timeline, practice areas). Even the seemingly similar get_bio and get_biography are clearly differentiated by their descriptions: one returns full background, the other returns press-ready versions. An agent can easily select the correct tool based on the user's query.
Naming Consistency5/5
All tools follow a consistent get_noun pattern (e.g., get_affiliations, get_bio, get_biography). This makes the tool surface predictable and easy to navigate for both agents and developers.
Tool Count4/5
17 tools is slightly above the ideal range of 3-15 for a knowledge base, but the count is justified by the breadth of information covered (bio, career, practice areas, publications, etc.). No tool seems redundant, and the set is well-scoped to a single attorney.
Completeness5/5
The tool surface covers all major aspects of an attorney knowledge base: biography, career timeline, practice areas, credentials, affiliations, publications, speaking engagements, trials, recognition, and contact information. There are no obvious gaps in the lifecycle of information about Jennifer Rebholz.