Skip to main content
Glama

Read company profile

readCompanyProfile
Read-onlyIdempotent

Read the company profile. get: reads the current company profile, the name and every editable field, plus the company notes (the memory entries Clera keeps about how this company hires), so you can see what is already filled. Run this first.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "command": "<command>"
    },
    "name": "readCompanyProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
commandYesWhich operation to run: get. The tool description explains each.

Output Schema

NameRequiredDescriptionDefault
commandYes
entriesNo
profileYes
diffBlockNo
memorySavedNo
fieldsUpdatedNo
memoryRemovedNo
skippedNarrativeNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already carry readOnlyHint, idempotentHint and openWorldHint=false, yet the description still adds real context: it discloses that the response includes Clera's private memory notes about how the company hires, and it states that inputs and results are recorded for usage tracking and support. That data-disclosure detail is not derivable from the structured fields.

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?

Short and front-loaded, with the most important instruction ("Run this first") placed early. The opening sentence restates the title and the "get:" prefix is slightly redundant with the one-value command enum, but overall there is little wasted 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 two-parameter, single-operation read tool with an output schema and full annotations, the description covers purpose, content of the response, ordering, and data handling. Nothing an agent needs in order to invoke 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%, so both parameters (orgId and the single-value command enum) are already documented in the schema. The description's "get:" line describes what the operation returns rather than adding syntax or constraints for the parameters, so it meets but does not exceed the baseline.

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 and resource ("Read the company profile") and enumerates the scope of what is read: the name, every editable field, and the company notes. The read-vs-edit distinction against editCompanyProfile is easy to infer from "so you can see what is already filled," 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?

"Run this first" gives explicit ordering guidance that tells the agent to call this before mutating the profile. There is no statement of when not to use it or of an alternative for cases like contact or funding lookups, 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