Skip to main content
Glama

Collide MCP

by com.collidemcp.api
OverviewDiscussionsAdmin

get_symbol

Read-only

Exact facts about code without opening the file: the signature, parameters, calls, span and hash of one symbol, or, omitting symbol, of every symbol in the module, with the notes anchored to it and whether the file passed the repo's check. Use it when a briefing lacks a fact; use blast_radius for who depends on it. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRepo-relative file path, e.g. src/auth.py.
symbolNoFunction, class or method name; omit for the whole module.
repo_idNoThe repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / repo_id / description
      Previous value: -"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."New value: +"The repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in."
    • changedInput schema / required
      Previous value: -[
-  "repo_id",
-  "path"
-]New value: +[
+  "path"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / path / description
      Added value: +"Repo-relative file path, e.g. src/auth.py."
    • addedInput schema / properties / repo_id / description
      Added value: +"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."
    • addedInput schema / properties / symbol / description
      Added value: +"Function, class or method name; omit for the whole module."
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "repo_id",
-  "path",
-  "symbol"
-]New value: +[
+  "repo_id",
+  "path"
+]
  4. Changed7 schema fields changed
    • removedInput schema / properties / path / description
      Removed value: -"Repo-relative file path, e.g. src/app/api.py."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • removedInput schema / properties / repo_id / description
      Removed value: -"Repository id — the git remote (e.g. github.com/acme/api) or a bare folder name; a #branch suffix scopes to that branch."
    • removedInput schema / properties / repo_id / title
      Removed value: -"Repo Id"
    • removedInput schema / properties / symbol / description
      Removed value: -"A symbol in the file — function, class, method, or constant name."
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedInput schema / title
      Removed value: -"get_symbolArguments"
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered and the trailing 'Read-only' is largely redundant. The description still adds real behavioral context: it reads facts 'without opening the file', describes what data is surfaced (notes anchored to the symbol, check status), and explains the fallback behavior when symbol is omitted.

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-loaded with the value proposition and what is returned, then the routing guidance. The first sentence is a long comma-chained list that borders on run-on, but every clause carries information and nothing is padding.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly, including the module-wide case and the attached notes/check status. Minor gaps remain: nothing about a nonexistent symbol or error behavior, which is acceptable but keeps it short of a 5.

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 all three parameters (path, symbol, repo_id) are already documented with examples and the omit-semantics for symbol and repo_id. The description restates the symbol-omission behavior but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 verb+resource (get one symbol's facts) and enumerates exactly what comes back: signature, parameters, calls, span, hash, anchored notes, and repo check status. It also carves out the module-wide variant when symbol is omitted, so an agent can distinguish it from blast_radius and get_briefing without opening a schema.

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?

Gives an explicit trigger ('use it when a briefing lacks a fact') and names the alternative plus its selecting condition ('use blast_radius for who depends on it'). Both the when and the when-not are stated, leaving nothing to inference.

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

All Collide MCP toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources