Skip to main content
Glama

The Very Lab

Company profile

get_company_profile
Read-onlyIdempotent

Who The Very Lab is: legal entity, address, contacts, working hours, response time, markets served.

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_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a closed-world, read-only, idempotent lookup, so the safety profile needs no restating. The description adds real value by disclosing what data is surfaced, which matters because no output schema exists; it stops short of saying whether the data is static or refreshed, or how contacts are formatted.

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?

One dense fragment with no filler, and the identity of the resource is front-loaded. The colon-list structure is efficient, though the missing verb makes it read slightly as a label rather than a statement of what the call does.

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 zero-parameter, read-only lookup with no output schema, enumerating the returned fields is the main thing the description must do, and it does that. Only minor gaps remain, such as whether the listed contacts/hours are the canonical support channel versus a general inquiry path covered by how_to_inquire.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies a parameterless call by framing the tool as a fixed profile lookup.

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 the resource concretely and enumerates the contents (legal entity, address, contacts, hours, response time, markets), so an agent knows exactly what this returns. It lacks a verb and does not explicitly differentiate itself from siblings like get_page or search_site, keeping it short of a 5.

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?

Usage is only implied: the field list signals this is the tool for 'who are you / where are you / how do I reach you' questions. There is no explicit when-to-use statement, no exclusions, and no alternative named (e.g., get_page for narrative content), leaving routing 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