Skip to main content
Glama

server

get_services

Read-onlyIdempotent

Use when you need to inspect Yari Infotech's 12 digital engineering services across Build, Connect, and Grow pillars. Returns a JSON array of service slugs, titles, pillars, summaries, and canonical URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
pillarNoFilter services by strategic pillar: 'build', 'connect', 'grow', or 'all' to retrieve every capability.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by describing the return payload shape (JSON array of slugs, titles, pillars, summaries, canonical URLs) and the fixed catalog size of 12, which sets expectations for result volume.

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?

Two tight sentences with zero filler. The usage trigger is front-loaded and the return-value summary follows immediately, which is exactly the order an agent needs.

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 single-parameter read-only listing tool with no output schema, the definition covers the trigger condition, the data domain, and the shape of the response. Nothing needed to select or call it correctly is missing.

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% and the enum values are already documented with a default of 'all,' so the schema does the heavy lifting. The description reinforces what the pillars mean in context but does not add filtering behavior, ordering, or combination semantics beyond the schema.

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?

States a specific verb+resource: retrieving the 12 digital engineering services, with scope across Build, Connect, and Grow pillars. The content type (service catalog) is distinct enough that it is unlikely to be confused with get_case_studies or estimate_project, though no sibling is named explicitly.

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?

Opens with an explicit trigger: 'Use when you need to inspect... the 12 digital engineering services,' which tells the agent the situation that selects this tool. It offers no exclusions or named alternatives for related lookups (e.g., case studies or project estimates), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources