Skip to main content
Glama
research-workflow-studio

research-workflow-studio

by BorgDiven

rws_code_find

Read-onlyIdempotent

Find existing implementations before building new code, returning exact identities and declared contracts. Supplied check evidence is not independent verification.

Instructions

Find existing implementations before building new code. Returns exact identities and declared contracts; supplied check evidence is not independent verification.

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": {
      "projectId": "<projectId>"
    },
    "name": "rws_code_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo
specRefNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "inference",
      -  "evaluation",
      -  "analysis",
      -  "report"
      -]New value: +[
      +  "training",
      +  "inference",
      +  "evaluation",
      +  "analysis",
      +  "report"
      +]
  2. First observedv0.3.3

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already specify readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context by stating that results include exact identities and declared contracts, and it warns that 'supplied check evidence is not independent verification.' This adds meaningful caveats beyond the annotations, though it does not cover pagination or result limits.

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 description is two sentences, front-loaded with the primary action and followed by a useful behavioral caveat. It is compact and every sentence adds value.

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

Completeness2/5

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

Given the tool has five parameters, a nested object, an enum, and no output schema, the description is too sparse to fully prepare an agent to invoke it correctly. It mentions the return content broadly but does not explain parameter meanings, filtering behavior, or result limits, leaving significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has five parameters with 0% description coverage, including a nested specRef object and a kind enum. The description provides no explanation of what query, kind, limit, specRef, or projectId mean or how they affect the search. It fails to compensate for the complete lack of schema parameter descriptions.

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 uses a specific verb and resource: 'Find existing implementations before building new code.' It clearly communicates a search/lookup function rather than creation or mutation. It does not explicitly contrast with the sibling registration tool rws_code_register, so it falls short of full sibling differentiation.

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?

The phrase 'before building new code' gives clear intended usage context and implies this tool should be used prior to code creation. However, it does not state explicit exclusions or name alternatives like rws_code_register, leaving some guidance implicit.

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