Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_find_callers

Find all call sites and definitions of a function or method across a workspace before changing its signature.

Instructions

Fast Cross-Repo Symbol Call-Site Locator (v10.0): finds all call sites and definitions of a function or method before changing its signature.

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": {
      "workspace": "<workspace>",
      "symbol": "<symbol>"
    },
    "name": "sqo_find_callers"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesFunction or method name.
max_hitsNoMax call sites to return (default: 25).
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It conveys that this is a read-style lookup ('finds') and that it is fast, but says nothing about permissions, whether results are truncated or ranked, whether call sites and definitions are returned in distinguishable form, or how cross-repo boundaries are determined.

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?

One front-loaded sentence states the capability and the motivating scenario efficiently. The '(v10.0)' version tag is filler that does not help an agent decide or invoke, which keeps it short of full marks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, two-required lookup tool with no output schema and no annotations, the description is adequate but thin. An agent still cannot predict the result structure (call sites vs. definitions, file/line granularity) or the search scope, which matters for a tool advertised as cross-repo.

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 the baseline is 3. The description adds only the 'cross-repo' framing, which slightly clarifies that 'workspace' may span multiple repositories; it adds nothing about matching semantics for 'symbol' (exact name vs. qualified path) or the effect of max_hits on truncation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it 'finds all call sites and definitions of a function or method', and adds a cross-repo scope. It does not explicitly differentiate itself from the code-search sibling, so an agent must infer the distinction, but the purpose itself is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied through the clause 'before changing its signature', which does hint at the refactor/pre-change scenario. There is no explicit when-not-to-use guidance and no named alternative among the many search-related siblings (sqo_code_search, sqo_blast_radius, sqo_edit_symbol).

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