Skip to main content
Glama

search_studio_files

Searches Studio project files line by line for a case-insensitive string to locate where a Workday field, function, or namespace is used.

Instructions

Full-text search across Studio project files. Searches line-by-line for a plain string (case-insensitive). Useful for finding where a specific Workday field, function, or namespace is used.

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": {
      "query": "<query>"
    },
    "name": "search_studio_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe string to search for (case-insensitive)
file_typeNoFilter by file type. Defaults to "all".
max_resultsNoMaximum number of matches to return. Defaults to 20.
project_nameNoLimit search to a specific project. Omit to search all projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden and it does disclose meaningful traits: plain-string not regex matching, case-insensitivity, line-level granularity, and project-wide scope by default. It stops short of describing what a match looks like (file path plus line number?), ordering, or any cost/limits behavior, which matters for a search tool with no output schema.

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?

Three short sentences, front-loaded with the core action, then matching semantics, then the motivating use case. Each sentence contributes distinct information and nothing is padded.

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 four-parameter search tool with no annotations and no output schema, the definition explains the input side well but leaves the return contract undefined — an agent cannot tell whether results are file paths, line excerpts, or match counts. Adequate as a minimum viable description, but the result shape gap is real.

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 query, file_type, max_results, and project_name are all documented in the schema including defaults and the enum. The description adds only the general notion of searching across projects, which weakly supports project_name but adds no syntax, matching, or filtering nuance beyond structured data.

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 names a specific verb and resource ('Full-text search across Studio project files') and narrows the mechanism ('line-by-line', 'plain string', 'case-insensitive'). It does not explicitly contrast itself with siblings such as list_project_files or read_integration_file, so an agent must infer the boundary between searching and listing/reading.

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

Usage Guidelines3/5

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

"Useful for finding where a specific Workday field, function, or namespace is used" gives a concrete positive use case, which is more than nothing. However, there is no statement of when not to use it (e.g. to enumerate files or read whole contents) and no named alternative, so the routing guidance is only implied.

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