Skip to main content
Glama

Symvanta

by com.symvanta

source

Read-onlyIdempotent

Raw file/git access at the indexed commit, for cloud agents with no clone; with a clone prefer your own Read/Grep/git. Ops:

  • read: content of filePath, whole file or slice startLine..endLine. ifHash (a prior read's hash) returns {unchanged:true}, no content. compact:true strips blank/comment-only lines.

  • list: files+subdirs at path. grep: ripgrep pattern (glob/pathPrefix). tree: layout from path. stat: size/lines/language/binary for filePath. blame: authorship for filePath. diff: fromSha..toSha. Keys: {op:"read",filePath:"src/a.ts"}, {op:"grep",pattern:"foo"}, {op:"list",path:"src"}. filePath is the file, path the directory. Gated by the Source Access add-on; else source_access_required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNoSee the tool description for each op. Omitted: inferred from the other args (pattern -> grep, fromSha/toSha -> diff, filePath/path -> read, nothing -> list).
globNogrep: limit to files matching this glob.
pathNolist/tree/diff: dir path in the repo (default root). On read/stat/blame it is read as filePath, on grep as pathPrefix.
limitNogrep: max matches.
queryNogrep: alias for pattern.
toShaNodiff: target commit (required), reachable from the indexed branch.
ifHashNoread: a prior read's hash; if it still matches, returns {unchanged:true}, no content.
compactNoread: strip blank/comment-only lines (heuristic; content no longer maps 1:1 to lines).
endLineNoread/blame: last line, 1-based.
fromShaNodiff: base commit (required), reachable from the indexed branch.
patternNogrep: ripgrep pattern (required; `query` is accepted as an alias).
feedbackNoOptional: report how a previous answer worked out; piggybacks on any call.
filePathNoread/stat/blame: the file to open (required; `path` is accepted as an alias).
maxDepthNotree: max recursion depth, default 3.
commitShaNoPin reads to one indexed revision (7-40 hex). Graph tools error with revision_not_indexed when it is not an indexed revision of the scoped repository, or revision_not_servable when that revision's graph was superseded by a later reindex, and echo the revision served back as commitSha; source ops read git objects, so any commit works there. Exception: a kept revision (revisions rows flagged architectureSnapshot) still serves map view:"architecture" as a preserved snapshot.
projectIdNoProject id from init/list_projects. Omit for the active project.
startLineNoread/blame: first line, 1-based.
pathPrefixNogrep: limit to files under this prefix.
repositoryNoRepository full name, e.g. "owner/repo". Omit when the project has one repository.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read/idempotent annotations, the description discloses operational details: reads happen at the indexed commit, ifHash suppresses content when unchanged, compact strips blank/comment-only lines, and each op's core behavior is summarized. No annotation contradiction exists; 'diff' and 'blame' are read-style introspection against git objects.

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?

The definition is densely packed but front-loaded with the reason for existence, then organized as a scannable op list, key examples, and a gating note. Every sentence adds operational value; there is no filler or repetition of schema descriptions.

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 7-op, 19-parameter tool with no output schema, the description covers scope, operation semantics, key parameter roles, representative call shapes, and access requirements. The remaining return-shape details are minor and inferable from the op names and schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds usable clarifications: the key examples show canonical argument shapes, 'filePath is the file, path the directory' disambiguates two overloaded parameters, and the op list maps operations to required arguments. This goes beyond a bare schema repeat.

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?

The opening line names a specific resource ('raw file/git access at the indexed commit'), ties it to a clear audience (cloud agents with no clone), and distinguishes it from local Read/Grep/git. The operation list then makes the tool's scope unmistakable.

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?

It explicitly states when to use this tool ('for cloud agents with no clone') and when not to ('with a clone prefer your own Read/Grep/git'). It also surfaces the prerequisite gate ('Gated by the Source Access add-on; else source_access_required'), so the agent can predict availability.

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

All Symvanta toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Tools generally target distinct operations—repository attachment, symbol resolution, graph traversal, source access, indexing health—and the detailed routing notes reduce ambiguity. A few pairs still overlap in intent (quick_lookup vs locate symbol, context vs ask_codebase), so it is not perfectly unambiguous.

Naming Consistency3/5

All names are lowercase snake_case and readable, but the set mixes verb_noun patterns like add_repository and list_projects with single-word nouns/verbs like context, history, map, relate, and source, plus one acronym (adr). There is no predictable convention across the full surface, though individual names are clear.

Tool Count3/5

25 tools is at the high end for a single MCP server and falls in the 'feels heavy' range. The breadth is justified by the code-intelligence/query domain, but the selection surface is large for an agent to navigate efficiently.

Completeness4/5

The code indexing, search, graph query, source access, history, ADR, test lookup, and scope estimation needs are well covered. Minor gaps remain—no detach/remove repository, no ADR content editing, and source access is gated by an add-on—but these are workable.

Resources