Skip to main content
Glama

get_intents_for_lines

Check a line range for overlapping intents to prevent merge conflicts and coordinate with team members.

Instructions

Get intents covering a specific line range.

Use this before modifying specific lines to check for conflicts:

  • Warns if the lines overlap with another team member's active intent

  • Shows the exact overlap range

  • Helps avoid merge conflicts and duplicate work

Returns overlap details so you can work around or coordinate with team members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endLineYesEnd line number (1-based, inclusive)
filePathYesPath to the file (relative to repo root)
repoPathYesLocal path to the repository root
startLineYesStart line number (1-based)
forkAuthorNoFork attribution; usually resolved by Muninn automatically — pass only for override / testing.
repoOriginNoGit remote origin URL. Auto-detected from repoPath via git if not provided.
workspaceIdNoWorkspace identifier; usually resolved by Muninn automatically — pass only for override / testing.
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses conflict-checking behavior and return of overlap details, but does not explicitly state the tool is read-only or describe side effects like rate limits or permissions.

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?

Concise: two sentences with bullet points. Front-loaded with purpose, then usage guidance. No superfluous words.

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?

No output schema, but description mentions return of overlap details. Explains core use case and behavior well. Lacks detail on output format and edge cases, but sufficient for selective use.

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 coverage is 100% with descriptions for all parameters. The description does not add further detail about parameter semantics beyond the schema, meeting the baseline but not exceeding it.

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 description clearly states the tool retrieves intents for a specific line range, and implies differentiation from sibling tool 'get_intents_for_file' which operates on entire files.

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?

Explicitly states when to use: before modifying lines to check for conflicts. Lists benefits (warns about overlaps, avoids merge conflicts) but does not mention when not to use or compare with alternative conflict-detection tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kawacode-ai/kawa.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server