Skip to main content
Glama

SourceGeek

Get schools a person follows

employee_profile_school_interests
Read-only

List the schools a member follows (id, name, url, follower count). Paged via page (50 per page).

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": {
      "usernameOrUrl": "<usernameOrUrl>"
    },
    "name": "employee_profile_school_interests"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
usernameOrUrlYesA profile username such as 'janedoe' or a public profile URL ending in /in/janedoe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new behavior: the fields returned and that results are paged at 50 per provider page. It does not say what happens for private/nonexistent profiles or whether partial results are possible.

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?

Two short sentences, front-loaded with the resource and scope, with the return fields and paging packed into tight parentheticals. Little is wasted, though the paging clause is terse enough to be ambiguous about how page and limit interact.

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 paginated read with full schema coverage and safety annotations, the description supplies the missing pieces an agent needs: the returned fields and pagination scale. Only minor gaps remain, such as behavior on invalid or private usernames and any ordering guarantee.

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 all three parameters are already documented, making 3 the baseline. The description adds the provider page size (50), which complements the schema's note that results beyond the provider page are not fetched, but it never mentions the limit parameter, leaving an agent to reconcile '50 per page' against limit's default of 10 and max of 100.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("List the schools a member follows") and even enumerates the returned fields (id, name, url, follower count). Alongside siblings like employee_profile_company_interests and employee_profile_group_interests, the resource noun 'schools' is the discriminator, and it is stated explicitly.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. public profile required), and no reference to the closely related interest tools it sits beside. The purpose statement implies the obvious case, but nothing tells an agent when to pick this over employee_profile_company_interests or employee_profile_group_interests.

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