Skip to main content
Glama
Sign In
ragnarok

ragnarok

by freyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_by_jira

Locate Obsidian notes containing a specific Jira key, such as ABC-123, to connect a ticket with related local documentation.

Instructions

The notes that contain a Jira key, for example ABC-123.

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": {
      "key": "<key>"
    },
    "name": "find_by_jira"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "find_by_jiraDictOutput",
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it never states that this is a read-only operation, whether matching is exact or substring, whether the key is case-sensitive, or whether one or many notes can be returned. Only the 'contains' phrasing hints at match semantics.

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?

A single short sentence with zero filler, and the identifying information comes first. It reads as a sentence fragment rather than a complete statement, but nothing is redundant.

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 one-parameter read lookup with an output schema, the definition is minimally sufficient, and it does supply a sample key value. It still leaves match semantics and result cardinality unstated, which matters for a finder tool.

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 0% and the schema only types `key` as a string with no description, so the description must compensate. The example 'ABC-123' does convey the expected key format, which is genuinely useful, but it does not explain matching behavior for the key.

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

Purpose3/5

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

The fragment identifies the resource (notes) and the filter (contain a Jira key), so an agent can infer it is a lookup by Jira key. But it lacks an explicit verb and offers no differentiation from the sibling `search` or `find_projects`, which plausibly overlap.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of `search` or `find_projects`, and no exclusions or prerequisites. Usage is only implied by the noun phrase 'the notes that contain a Jira key'.

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