Skip to main content
Glama

Developh studio profile

studio_info
Read-only

Facts about Developh, a design and development studio in Lisbon, Portugal: address, team, services, sectors with case studies, timelines, how projects are priced and how to get in touch.

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": "studio_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoAnswer language: English (en) or European Portuguese (pt).en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the scope of facts included but does not discuss return format, freshness, or limitations; with annotations present, this is adequate but not rich.

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?

The definition is a single front-loaded sentence with a colon-delimited list of included facts. It is efficient and every item helps scope the tool, with no redundant wording.

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?

For a simple one-parameter profile lookup with no output schema, the description covers the content scope and annotations cover safety. The main missing piece is sibling routing, but otherwise it is complete enough to call correctly.

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?

The single locale parameter is fully documented in the schema with an enum and default, and schema description coverage is 100%. The description adds no parameter-level meaning, so the baseline of 3 applies.

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 resource, the Developh studio profile, and enumerates the facts it returns: address, team, services, sectors, pricing, and contact details. It is clearly a read-only profile lookup, though it does not explicitly distinguish itself from list_case_studies despite mentioning case studies.

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?

No explicit when-to-use or when-not-to-use guidance is given. The content list implies it is for general studio facts, but it does not route the agent to request_contact for contact or list_case_studies for case studies, leaving sibling selection to inference.

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